Skip to main content
Glama

Search Gozatu! articles

search
Read-onlyIdempotent

Search the Gozatu! guide (German) to Donostia-San Sebastián and the Basque Country: pintxos bars, restaurants, recipes, sights, day trips, festivals, practical travel tips. Returns matching articles with id, title and url. Use fetch with the id to read an article. Queries work best in German or with local names (e.g. "Gilda", "Txakoli", "Parte Vieja").

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": {
      "query": "<query>"
    },
    "name": "search"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYesSearch terms, e.g. "beste Pintxos Parte Vieja" or "Flughafen Bilbao Bus".

Output Schema

NameRequiredDescriptionDefault
resultsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world behavior, so the safety profile is covered. The description adds genuine context beyond that: the corpus is German-language and geographically scoped, and queries succeed best with German terms or local names such as 'Gilda' and 'Txakoli'. It does not mention result limits or pagination, which is the remaining gap.

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?

Three short sentences with no filler. Scope comes first, the return shape and follow-up second, and the query-crafting tip last — a sensible front-to-back ordering for an agent reading it once.

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?

The presence of an output schema means the id/title/url listing need not be expanded, and the description correctly points to fetch for the full article. For a one-parameter search tool it is nearly complete; only ranking, result-count limits, and behavior on zero matches are unstated.

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

Parameters4/5

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

With a single parameter at 100% schema coverage, the schema already documents 'query' and supplies examples. The description nonetheless adds meaning the schema does not: recommended query language (German) and the value of using local proper names, which materially changes how the agent writes the query.

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?

The description names a specific verb and resource (search the Gozatu! guide) and enumerates the covered domains: pintxos bars, restaurants, recipes, sights, day trips, festivals, practical tips. It also pins down the geographic and linguistic scope (German-language guide to Donostia-San Sebastián and the Basque Country), so an agent can tell exactly what corpus is being searched.

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?

It gives a clear follow-up path — 'Use fetch with the id to read an article' — which tells the agent this tool is the entry point and fetch is the reader. Query-formulation guidance ('work best in German or with local names') is a concrete usage condition. It stops short of saying when to prefer ask_gozatu or find_places instead, so it is clear context without explicit exclusions.

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