Skip to main content
Glama

El truco del Guardián

ver_estado

Read-onlyIdempotent

Muestra tus cartas, la mesa, los puntos y qué podés hacer ahora.

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": "ver_estado"
  }
}

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

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so the safety profile is covered. The description adds genuine value by disclosing the payload contents — cards, table, points, available actions — which matters because there is no output schema. It does not mention pagination, freshness, or error behavior, but those are minor for a state read.

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 sentence with no filler, front-loading the returned contents. 'La mesa' is slightly vague but consistent with the game's domain vocabulary.

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 one-parameter, read-only state tool with strong annotations, the description covers purpose and roughly what comes back. Since no output schema exists, a hint about the response shape is valuable and is provided at a high level; nothing an agent needs to invoke it correctly is missing.

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 one parameter at 100% schema description coverage, and the schema already explains that 'partida' comes from 'nueva_partida'. The description adds no additional meaning about the parameter, so the 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?

States a specific verb ('Muestra') and enumerates the resource contents: your cards, the table, the points, and available actions. An agent can tell this is the state-reading tool. It does not, however, differentiate itself from siblings like 'tabla_de_rivales' or 'reglas', which also surface game information.

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?

The phrase 'qué podés hacer ahora' implies the tool is for orienting before choosing a move, and the required partida parameter implies it follows 'nueva_partida'. No explicit when-to-use or when-not guidance is given, and no alternative (e.g., 'tabla_de_rivales') is named.

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