Skip to main content
Glama

About Guía Extranjeros

about_guia
Read-onlyIdempotent

Describes Guía Extranjeros: what it covers, languages, number of current guides by topic, data freshness and what is not included.

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": "about_guia"
  }
}

Input Schema

NameRequiredDescriptionDefault
langNoLanguage of the guides: "es" Spanish, "en" English, "uk" Ukrainian. Default: Ukrainian for Cyrillic queries, otherwise English.

Output Schema

NameRequiredDescriptionDefault
langYes
linkYes
as_ofNo
summaryYes
disclaimerYes
guides_by_topicNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/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, so safety is covered. The description adds genuine behavioral context beyond that: it discloses what metadata is returned (guide counts by topic, data freshness) and, unusually, what is *not* included, which sets agent expectations. It stops short of describing format or size of the response.

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?

A single front-loaded sentence with no wasted words; the list of covered facets is compact and each item carries information.

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?

With an output schema, full annotation coverage and a fully documented single parameter, the description only needs to frame scope and expectations — which it does, including the exclusions caveat. Minor gap: it does not hint at when an agent should consult it relative to the content tools.

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?

Only one parameter (lang) exists and its schema description is complete, including enum meanings and a default heuristic. The description itself says nothing about language selection, so it adds no meaning beyond the schema — 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?

The description gives a specific verb ('Describes') and a clearly named resource ('Guía Extranjeros'), then enumerates the facets it reports: coverage, languages, guide counts by topic, data freshness and exclusions. That makes it easy to separate from get_guide and search_guides, which fetch actual guide content, though it never names those siblings 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: an agent can infer this is the orientation/meta tool to call before or instead of fetching guides. There is no explicit 'use this when…' statement, no statement that it should precede search_guides, and no exclusion criteria.

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