Skip to main content
Glama

Ver cómo va una solicitud

estado_solicitud
Read-only

Estado de una solicitud ya enviada. Hace falta el enlace privado que devolvió pedir_reserva (o su código y su clave).

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

Input Schema

NameRequiredDescriptionDefault
claveNo
codigoNo
enlaceNoEl enlace privado de la solicitud

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered. The description's real addition is the access requirement — a private link or code+key pair is needed to look anything up — which is behavioral context the annotations do not carry. It says nothing about what happens with an invalid or expired credential, which would be the most useful remaining detail for an auth-gated read.

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 short sentences, no filler: the first establishes what the tool returns, the second what it needs to be called. The prerequisite is front-loaded after the purpose statement, exactly the order an agent needs.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a read-only lookup with no output schema, the description covers invocation but not the result: it never indicates what a status consists of or which states are possible, which is what an agent needs to interpret the response. That is the main gap for an otherwise simple, adequately specified tool.

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 only 33%: codigo and clave have no descriptions at all. The description compensates by establishing that enlace is interchangeable with codigo + clave and by naming pedir_reserva as the source of those values, an either/or relationship the flat schema cannot express. It stops short of stating whether codigo and clave must be supplied together.

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?

"Estado de una solicitud ya enviada" names a specific resource (a submitted request) and the operation (read its status), which cleanly separates it from pedir_reserva, the tool that creates such requests. It does not explicitly label itself as the read-only counterpart, but the distinction is inferable from "ya enviada".

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?

The prerequisite is stated directly: the caller must already have sent a request via pedir_reserva and hold the private link (or codigo + clave) it returned. That tells the agent when this tool applies. It does not name a when-not condition or an alternative status mechanism, which keeps it short of a 5.

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