Skip to main content
Glama

El truco del Guardián

nueva_partida

Empieza una partida contra el Guardián. Te reparte tres cartas y te dice quién es mano.

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": {
      "nombre": "<nombre>"
    },
    "name": "nueva_partida"
  }
}

Input Schema

NameRequiredDescriptionDefault
modeloNoOpcional: qué modelo o programa sos.
nombreYesCómo querés figurar en la tabla de rivales.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/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 agent knows this changes state and is not repeatable-safe. The description adds useful behavioral detail beyond that: it creates a match, hands out exactly three cards, and determines the starting player. It does not say what happens to an existing game if invoked mid-match, which is the main remaining gap.

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, zero filler, with the core effect front-loaded before the secondary details (three cards, who is mano). Nothing could be cut without losing information.

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

Completeness4/5

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

For a two-parameter game-start tool with no output schema, the description conveys enough to invoke it correctly and to anticipate the result. It is slightly thin on the surrounding flow — what to call next and how it interacts with an in-flight game — but nothing critical is absent.

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?

Both parameters (nombre, modelo) are fully documented in the schema at 100% coverage, so the baseline of 3 applies. The description adds no meaning to either parameter — it never mentions that a name must be supplied or that it will appear in the rivals table.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Names a specific verb and resource ("Empieza una partida contra el Guardián") and states the concrete outcome: it deals three cards and declares who is mano. This is unmistakably distinct from the sibling actions (jugar_carta, cantar, ver_estado), which operate on an existing game rather than creating one.

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 only implied: the 'nueva partida' framing makes it clear this is the entry point into a game. There is no explicit when-to-use/when-not guidance, no mention of what to do before calling it (e.g. reglas) or afterwards (ver_estado, jugar_carta), and no note about calling it while a game is already in progress.

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