Skip to main content
Glama

El truco del Guardián

responder

Responde a lo que te cantó el Guardián: quiero o no_quiero.

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": {
      "partida": "<partida>",
      "respuesta": "<respuesta>"
    },
    "name": "responder"
  }
}

Input Schema

NameRequiredDescriptionDefault
partidaYesEl id de la partida que te dio nueva_partida.
respuestaYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already flag this as a non-read-only, non-idempotent, non-destructive, closed-world action, so the description must add the game-level consequences. It does not say what accepting ('quiero') versus declining ('no_quiero') actually does to game state, whether the choice is final, or what happens if the call is no longer pending.

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?

A single short sentence with no filler and the key information front-loaded. It is efficient, though the terseness is a symptom of under-specification rather than exemplary brevity.

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

Completeness2/5

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

For a state-mutating game action with two required parameters, no output schema, and only one annotated behavior, the definition leaves the agent without the consequences of each reply or the post-response state. An agent could invoke it but could not predict the outcome.

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

Parameters2/5

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

Schema coverage is 50%: 'partida' is documented in the schema, and 'respuesta' is an enum whose two values the description merely restates without explaining their meaning or effect. It adds essentially no semantics beyond what the schema already provides.

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 concrete verb ('Responde') and the specific object being responded to ('lo que te cantó el Guardián'), and enumerates the two valid replies. It is reasonably distinguishable from the sibling 'cantar', which is the initiating side of the exchange, though the description never says so 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 implied: call this when the Guardian has made a call to you. There is no explicit when-not guidance, no mention of what to do if no call is pending, and no named alternative tool.

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