Today's Puerto Rico briefing: the latest English news summaries from 787daily, each linked back to the original Spanish-language source. Returns summaries + links only.
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | How many stories to return (default 10) |
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
Input schema / $schemaPrevious value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the burden. It explicitly states the return format ('summaries + links only') and the scope ('latest'), making the behavior predictable. It doesn't mention potential caveats like rate limits, but for a simple read tool this is sufficient.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two sentences, front-loaded with the core purpose, and every word adds value. No fluff or redundancy.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a simple tool with one optional parameter and no output schema, the description gives the essential return value and source. It lacks explicit disambiguation from siblings, but the 'daily briefing' framing is enough for most use cases.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The only parameter, 'limit', is already fully described in the schema (including default and range). The description adds no extra meaning about the parameter, so it doesn't go beyond what the schema provides. Baseline 3 is appropriate.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly identifies the tool as a daily briefing for Puerto Rico, specifying the content (English news summaries from 787daily) and output (summaries + links to Spanish sources). This differentiates it from siblings like search_news or get_by_entity.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description implies the tool is for retrieving today's briefing, but it doesn't explicitly state when to use it versus alternatives like search_news or keyword_search_news. There's no mention of exclusions or alternative tools, so guidance is only implied.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Most tools have clearly distinct purposes: ask synthesizes answers, search_news does semantic retrieval, keyword_search_news does keyword matching, and the get_/list_ tools target specific data types. However, search_pr_news is a redundant alias, and get_by_entity vs get_by_municipality overlap on place queries, creating minor ambiguity.
Tool names use a mix of prefixes (get_, list_, search_) and include a bare verb (ask), which is not fully consistent. The legacy alias search_pr_news further deviates from the pattern, though the rest are readable and predictable.
With 13 tools spanning news, Q&A, weather, cost-of-living, and safety, the count fits the server's broad purpose without being excessive. Each major domain has dedicated tools, and despite one redundant alias, the set remains well-scoped.
The tool set covers article discovery, synthesis, weather, demographics, and safety statistics, providing solid domain coverage. Minor gaps include no full-text article retrieval and no dedicated section browsing, but summaries and links make these workable.