Skip to main content
Glama

Vizo: out-of-home advertising in Paraguay and Uruguay

Ficha de un espacio

ficha_espacio
Read-only

Todos los datos públicos de un espacio a partir del id devuelto por buscar_espacios (ubicación, coordenadas, formato, tipo, página).

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": {
      "id": "<id>"
    },
    "name": "ficha_espacio"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesid del espacio, ej.: py-1

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/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 profile is covered. The description adds meaningful context beyond that: only public data is returned, and the parenthetical lists the categories of fields the agent will receive, which helps it decide whether the call is worth making.

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 sentence with the resource and the id source front-loaded, followed by a compact parenthetical field list. No filler, no repetition of the title.

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-parameter read tool with full annotation coverage and no output schema, the description supplies what is needed: the id's origin and the shape of the returned data. It stops short of describing error behavior for an invalid id, which is the only notable gap.

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?

Schema coverage is 100% and the single id parameter is documented with an example, so the baseline is 3. The description adds provenance the schema does not: the id must be one returned by buscar_espacios, which prevents the agent from inventing identifiers.

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 states a specific resource (all public data of a space) and the key it is fetched by (the id returned by buscar_espacios), and it enumerates the data categories returned (location, coordinates, format, type, page). It implicitly distinguishes itself from the search sibling by framing itself as the detail lookup for a single id, though it never names a contrasting alternative 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?

It gives clear usage context: call this with an id obtained from buscar_espacios, which tells the agent this is the follow-up detail step after a search. It does not state when not to use it or how it differs from comparar_espacios, but the sequencing guidance is unambiguous.

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