Skip to main content
Glama

El truco del Guardián

irse_al_mazo

Destructive

Abandona la mano actual. El Guardián se lleva lo que valía el truco.

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>"
    },
    "name": "irse_al_mazo"
  }
}

Input Schema

NameRequiredDescriptionDefault
partidaYesEl id de la partida que te dio nueva_partida.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so safety is covered upstream. The description adds genuine context beyond that — the hand is abandoned and a cost is incurred ("El Guardián se lleva lo que valía el truco") — but the penalty is phrased poetically rather than as a concrete scoring consequence, leaving the exact effect on the game state unclear.

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?

Two short sentences with the action stated first and the consequence second; nothing is padded. The second sentence is atmospheric but does carry the cost information, so it earns its place despite the metaphorical phrasing.

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 single-parameter destructive action with no output schema, the description conveys the action and that something is lost, which is the minimum an agent needs. It does not say whether folding is irreversible, whether it ends the game or just the hand, or what state the agent will be in afterward.

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?

There is a single parameter with 100% schema description coverage, and the schema already explains that partida is the id returned by nueva_partida. The description adds no further meaning about the parameter, so the baseline of 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?

"Abandona la mano actual" gives a concrete verb and scope, translating the jargon name 'irse al mazo' into an understandable action (folding the current hand), which is distinguishable from siblings like jugar_carta or responder. It stops short of relating itself explicitly to any sibling, so it is clear but not differentiating by comparison.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no statement of when to fold versus continuing to play, no mention of alternatives such as cantar or responder, and no preconditions. Usage is only inferable from the general meaning of abandoning a hand.

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