Skip to main content
Glama

Cadena Láser — noticias y radios de Río Tercero

Noticias de un pueblo de la zona

noticias_de_localidad
Read-only

Las últimas noticias de un pueblo de la zona de Río Tercero (Almafuerte, Tancacha, Embalse, Hernando, Corralito, Villa Ascasubi, Villa del Dique, Villa Rumipal, Los Cóndores, Pampayasta, Tercero Arriba), de Cadena Láser y de los medios de la región. Para Río Tercero, ultimas_noticias con la sección «locales». (Latest news from a town near Río Tercero.)

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "localidad": "<localidad>"
    },
    "name": "noticias_de_localidad"
  }
}

Input Schema

NameRequiredDescriptionDefault
cantidadNoCuántas notas traer (1 a 20).
localidadYesEl pueblo: almafuerte (Almafuerte), tancacha (Tancacha), embalse (Embalse), hernando (Hernando), corralito (Corralito), villa-ascasubi (Villa Ascasubi), villa-del-dique (Villa del Dique), villa-rumipal (Villa Rumipal), los-condores (Los Cóndores), pampayasta (Pampayasta), tercero-arriba (Tercero Arriba).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety and scope profile is covered structurally. The description adds the provenance of the data (Cadena Láser plus regional media), which is useful context. It does not say anything about freshness, pagination, or what a returned item contains, so it goes only modestly beyond the annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The core scope statement is front-loaded, but the long parenthetical town list duplicates the enum verbatim and inflates the sentence. The trailing English gloss is a reasonable convenience yet repeats the opening. Tightening the locality enumeration would make the routing rule more prominent.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple read-only list tool with full schema coverage and annotations, the description is nearly sufficient: it establishes scope, sources, and the one important sibling exclusion. The remaining gap is the absence of any hint about the shape of the results (a list of notes, presumably with title/date/link), which there is no output schema to supply.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100% and the localidad enum already spells out every accepted value, so the description's re-listing of the same towns is redundant rather than additive. It says nothing about the cantidad parameter or the 1–20 bound. Baseline 3 is appropriate when the schema carries the semantics.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ("Las últimas noticias de un pueblo de la zona"), enumerates the covered towns, and names the sources (Cadena Láser and regional outlets). It also explicitly distinguishes itself from the sibling ultimas_noticias for the Río Tercero case, so an agent can separate the two without opening either schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives an explicit routing rule: for Río Tercero use ultimas_noticias with the «locales» section instead of this tool. That is a genuine when-not statement. It stops short of addressing the other plausible alternative, buscar_noticias, for older or topic-based searches, leaving that inference to the agent.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources