Skip to main content
Glama

Buscar historias y guías

buscar_historias
Read-onlyIdempotent

Use this when the user asks about the history of a place or a building, what stood there before, how it changed over the centuries, or wants an audio guide for a walk. Lists the Builtalist stories of places through time (the Acropolis, the Alhambra, the Prado…) and its audio guides, with a short summary and a link to each.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "buscar_historias"
  }
}

Input Schema

NameRequiredDescriptionDefault
textoNoA place, a building or a city: "Alhambra", "Madrid". Without it, all of them.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already cover safety (readOnly, idempotent, non-destructive, closed-world), so the description correctly focuses on content: it discloses the return shape (short summary plus a link per story/guide), which is valuable since there is no output schema. It does not discuss pagination or result limits, a minor gap.

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

Conciseness4/5

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

Front-loads the when-to-use condition, then a single sentence on what is returned. Slightly dense but every clause (triggers, content, return shape) earns its place; 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 one-optional-parameter search tool with no output schema, the description covers triggers, the corpus searched, and the return shape. Only pagination/result-size 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% and the schema description already explains that 'texto' is a place/building/city and that omitting it returns all. The description adds no syntax or formatting meaning beyond that, so the baseline 3 applies.

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 ('Lists the Builtalist stories of places through time ... and its audio guides') with concrete named examples (Acropolis, Alhambra, Prado). The content domain is clearly distinct from siblings like buscar_obras or buscar_exposiciones, though no sibling is named explicitly.

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?

Opens with explicit trigger conditions: user asks about the history of a place or building, what stood there before, how it changed, or wants an audio guide. This is strong positive guidance, but no exclusions or alternative tools are mentioned.

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