Skip to main content
Glama

El truco del Guardián

cantar

Canta envido, real_envido, falta_envido, truco, retruco o vale_cuatro. También sirve para subir la apuesta cuando te cantan.

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

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/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 mutating, non-repeatable nature is known without the description. The description adds little beyond that: it does not say whether an illegal call is rejected, what happens to the game state or turn after singing, or whether a raise must exceed the current bet. With annotations carrying the safety profile, a 3 is appropriate.

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 compact sentences, front-loaded with the action and its options, with no filler. The phrasing is efficient, though the second sentence's referent ('cuando te cantan') is slightly loose about what counts as being called.

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, no-output-schema game action, the description covers the what but not the outcome: it is silent on the resulting turn/state changes, failure conditions, and the interaction with 'responder' or 'ver_estado'. Adequate but with visible gaps for an agent that must decide between this and neighboring tools.

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 50%: 'partida' is documented in the schema and 'canto' is an enum. The enumeration of the six cantos in the description mirrors the enum rather than adding meaning, and there is no explanation of game-level significance or ordering constraints between cantos. Baseline 3 given the schema does the heavy lifting.

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?

Names a specific action (cantar) and enumerates exactly the six possible calls, mapping directly onto the enum, so an agent knows what the tool produces. It also covers the second use case (raising the stake when called). It never names a sibling or clarifies the boundary with the related 'responder' tool, so it stops short of full sibling differentiation.

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?

Two clear situations are given: to declare envido/truco-family calls, and to raise the bet when the opponent has called. No explicit exclusions or named alternatives are provided, so the agent must infer the division of labor with 'responder' and 'jugar_carta' on its own.

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