MCP Series Part 5: How Resources and Parameterized URIs Feed Live Data to LLMs

·1 views

A technical deep dive from DEV Community explains the distinction between MCP Resources and Tools in large language model architectures, where Resources serve as read-only data sources and Tools represent executable actions with potential side effects. Dynamic Resources return live, changing data on every read rather than a fixed snapshot, making them suitable for real-time information like sprint progress or issue counts. Parameterized URIs allow a single resource handler to serve multiple instances, such as per-project statistics, by parsing identifiers directly from the URI path. The host system decides when to inject Resources into context, enabling it to supply only the relevant data — for example, loading stats for the active project rather than all projects at once. The article also highlights the importance of marking dynamic Resources explicitly in their descriptions so the LLM knows to re-fetch them when fresh data is required.

Read the full story at DEV Community

This is an AI-generated summary. ShortSingh links to the original source for the complete article.

Discussion (0)

Why AI agents mishandle empty tool results — and how to fix it

Developers building AI agents frequently encounter a subtle failure mode where tool calls return empty results without explaining why, leaving agents unable to respond correctly. A single empty result set can stem from at least three distinct causes — a bad query, a stale data index, or a backend timeout — each requiring a different corrective action. Engineers have proposed that tools should return structured failure states with labels, supporting evidence, and a suggested retry interval, rather than treating all empty responses as equivalent. However, defining meaningful thresholds — such as what counts as a 'stale' index — introduces subjective calibration decisions that may not suit every use case. The broader issue is framed as an authority boundary problem: the assumptions baked into a tool's failure logic are set by its author, who may not anticipate the contexts in which the tool will eventually be deployed.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

Developer Builds AI Paper Ranking Tool to Cut Weekly arXiv Review Time by 80%

A developer working on the Paper List project within the OpenNomos ecosystem built a personalized research paper ranking engine to address the inefficiency of manually browsing arXiv each week. The tool uses text embeddings and cosine similarity to score papers by relevance to a user's specific project description, rather than relying on keyword matching or citation counts. Starting as a 200-line Python script, the system learns from user feedback over time, improving its recommendations as papers are saved or dismissed. In practice, the tool reduced the developer's weekly paper review time from roughly five hours to 45 minutes, while surfacing more relevant results per session. The developer notes the improvement stems not from complex AI, but from applying a smarter filtering approach to an otherwise noisy discovery process.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

ServeSense vs FileZilla Server: 2026 Feature and Security Comparison

A July 2026 comparison evaluates ServeSense and FileZilla Server across security, automation, and deployment criteria to help organizations select a file transfer solution. Both platforms support FTP, FTPS, and SFTP protocols, but ServeSense offers additional features including real-time monitoring dashboards, REST API, webhooks, and event triggers that FileZilla Server largely lacks. On the security front, ServeSense provides multi-level brute-force protection, DoS mitigation, and anti-timing attack controls, while FileZilla Server offers only basic protections. ServeSense is also notable for supporting non-administrator operation and a lightweight, zero-dependency installation, whereas FileZilla Server follows a more traditional setup suited to standard file transfer needs. FileZilla Server remains a widely adopted open-source option for straightforward use cases, while ServeSense targets DevOps, managed service providers, and enterprise workflows requiring greater automation and security.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

Rivalry Radar Uses Gemini AI and Snowflake to Rank World Cup Fan Passion Live

A developer built Rivalry Radar, a web app that lets football fans post 280-character reactions to any World Cup matchup and rates their emotional intensity on a scale of 1 to 10. Google's Gemini AI instantly classifies the sentiment of each submission and generates a short stadium-announcer-style verdict based on the latest fan takes for a given rivalry. Snowflake serves as the data warehouse, storing all submissions and computing a live Heat Index that ranks which rivalry is generating the most passion at any given moment. The project was submitted to the DEV Community's Weekend Challenge: Passion Edition, targeting the Best Use of Google AI and Best Use of Snowflake categories. The app's goal is to turn the flood of unstructured fan commentary that typically vanishes into group chats into measurable, rankable data.

0 comments Read more at DEV Community