Keyword search over 787daily's Puerto Rico news archive by title/summary and optional section. Returns matching article summaries with links to the originals. For semantic/vector search, use search_news.
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | Max results (default 20) | |
| query | No | Keyword search over title + summary | |
| section | No | Filter to one section slug |
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 full burden of disclosure. It states the search scope (title/summary), optional section filtering, and return format (article summaries with links). It does not cover edge cases like empty results or error behavior, but the core behavioral contract is transparent.
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, no filler. The first sentence defines the operation and scope; the second provides the alternative tool. Every word contributes meaningful information.
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?
Given the tool's simplicity (0 required params, simple filters), the description fully covers scope, filtering, return format, and alternative. Limit default is documented in the schema, and there is no output schema requiring return value explanation. No missing pieces.
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?
Input schema has 100% coverage with descriptions for all three parameters, including the default for limit and the enum for section. The description adds minimal semantic value beyond the schema, only echoing 'by title/summary' and 'optional section.' 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 uses a specific verb 'keyword search' and clearly identifies the resource (787daily's Puerto Rico news archive) and scope (by title/summary with optional section). It explicitly distinguishes from sibling search_news, leaving no ambiguity about the tool's purpose.
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?
Provides explicit guidance on when to use this tool versus alternatives: 'For semantic/vector search, use search_news.' This directly addresses the decision between keyword and semantic search, which is the key usage distinction among siblings.
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.