Skip to main content
Glama

El truco del Guardián

jugar_carta

Tira una de tus cartas, por ejemplo "1 de espadas" o "7 de oro".

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

Input Schema

NameRequiredDescriptionDefault
cartaYesLa carta, como "1 de espadas", o su posición en tu mano (1, 2 o 3).
partidaYesEl id de la partida que te dio nueva_partida.

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 declare readOnlyHint=false, idempotentHint=false and destructiveHint=false, so the mutation profile is covered externally. The description adds nothing beyond the bare action: it does not say the card leaves your hand, that the turn passes, or what happens on an illegal card.

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 front-loaded sentence with no padding and a helpful example, though its brevity borders on under-specification for a state-changing game action.

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 two-parameter action with full schema coverage and annotations carrying the safety profile, the essentials are present. Still missing are post-action effects (hand shrink, turn passing) and the placement of this action relative to cantar/responder.

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?

Schema coverage is 100% and the schema already documents both parameters, including the same example formats and the numeric hand-position alternative. The description merely repeats the card-format example, adding no syntax or constraint beyond the schema, so 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?

"Tira una de tus cartas" gives a concrete verb (discard/play) plus the resource and two literal examples of card values, so the action is unmistakable. It does not differentiate from siblings such as cantar or responder, which are also turn actions.

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 play a card versus declaring (cantar) or responding (responder), no prerequisites such as needing partida from nueva_partida (only implied by the schema), and no mention of turn order or legality of the play.

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