INPUT · buscador

Buscar notas de INPUT

buscar_notas

Busca notas publicadas en INPUT (magazine cultural de Buenos Aires) por palabras: lugares, artistas, discos, películas, muestras, juegos, cuentas. Devuelve título, bajada, sección, fecha y link.

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": {
      "consulta": "<consulta>"
    },
    "name": "buscar_notas"
  }
}

Input Schema

Name	Required	Description
`eje`	No	Sección opcional.
`limite`	No	Cantidad máxima de resultados (por defecto 8).
`consulta`	Yes	Palabras a buscar, por ejemplo «bar escondido Boedo» o «disco de cumbia».

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 3, 2026

TDQS

A3.6/5.0

Behavior3/5

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

No annotations are supplied, so the description carries the load. It usefully discloses the return fields (título, bajada, sección, fecha, link), which compensates for the missing output schema, and 'Busca' implies non-mutating behavior. It says nothing about result limits, pagination, or empty-result behavior, which are real gaps for an unannotated tool with a 'limite' cap of 20.

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

Conciseness5/5

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

Two sentences, front-loaded with the search action and source, second sentence covering return values. No filler.

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 keyword search with full schema coverage and no annotations, this is nearly complete: it identifies the corpus, the query semantics, and the returned fields in place of a missing output schema. Only result-count/pagination behavior is left unstated.

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 coverage is 100%, including enum values and a documented default of 8 for limite, so the schema already does the heavy lifting. The description adds the notion of free-text keyword search and the kinds of entities that work as keywords, but does not touch the 'eje' section filter or the result cap.

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

Purpose4/5

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

States a specific verb and resource ('Busca notas publicadas en INPUT') and identifies the publication as a Buenos Aires cultural magazine, plus enumerates the entity types searched. It implicitly reads as the broad search versus the domain-specific siblings (buscar_discos, buscar_lugares), but never names them explicitly.

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

Usage Guidelines3/5

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

Usage is only implied: listing lugares, artistas, discos and juegos suggests this is the cross-topic search, and the sibling names make the alternative obvious to a careful reader. There is no explicit when-to-use or when-to-prefer-a-sibling statement.

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

All INPUT · buscador tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?