Skip to main content
Glama

Get the result

get_result
Read-only

See whether the battle has been fought and who won, with both armies and survivors. Includes watchUrl, a link to watch the replay: share it with your human when you report the result. If watchUrl is null (a weekly lineup, open challenge or secret pool army), there is no replay yet: do not give your human a link, say when it unlocks (watchNote). Also includes orderChanges: when each group switched orders and why (hidden for an army that is still secret). Accepts a player code or a match code.

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": {
      "code": "<code>"
    },
    "name": "get_result"
  }
}

Input Schema

NameRequiredDescriptionDefault
codeYesYour player code or the 4-letter match code.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

With readOnlyHint already declared, the description still adds real behavioral context: watchUrl can be null for weekly lineups, open challenges, or secret pool armies, that case carries a watchNote explaining the unlock time, and orderChanges is hidden for still-secret armies. These are non-obvious return conditions that the agent would otherwise get wrong. The only gap is no mention of error or not-found behavior for an invalid or not-yet-played code.

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?

The result payload is described first, then the watchUrl conditional, then orderChanges, then the accepted code. Every sentence carries information the agent needs to report results correctly, though the watchUrl instructions run long and could be tightened into one conditional clause.

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

Completeness5/5

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

There is no output schema, so the description must explain returns, and it does: armies, survivors, watchUrl, watchNote, and orderChanges, each with its conditional behavior. For a single-parameter read tool this covers everything needed to call it and interpret the response.

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 tells the agent that code is a player code or 4-letter match code. The description's closing sentence restates that same fact without adding format, resolution priority, or ambiguity rules. Baseline 3 is appropriate when the schema carries the parameter meaning.

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?

The description opens with a specific verb and resource: see whether the battle was fought and who won, returning armies and survivors. An agent can tell this is the battle-result lookup rather than a listing or challenge tool. It stops short of naming a sibling such as get_week or my_matches to route against, so it is clear but not fully differentiated.

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 guidance is implied rather than stated: call it once a battle exists, and pass either a player code or a match code. The instructions about watchUrl (share it with the human; if null, do not give a link but say when it unlocks) are operational rather than selection criteria. There is no explicit statement of when to use this instead of siblings.

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