Skip to main content
Glama

Resolve a mission matchup

get_mission_matchup
Read-onlyIdempotent

Resolves two force dispositions, in the current mission pack or a named one, to the primary mission each side plays (its card: scoring awards, caps, actions, timing), the terrain layouts and deployments for the pairing, and canonical URLs and reference ids for each. Pass each value by id, slug, or name; an unknown or ambiguous value is refused with the valid options. Rules text is withheld: award criteria and card text come back empty, and the textSources of each award names the upstream file and the record id holding its scoring condition, so fetch that file to say what an award scores.

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": {
      "yourDisposition": "<yourDisposition>",
      "opponentDisposition": "<opponentDisposition>"
    },
    "name": "get_mission_matchup"
  }
}

Input Schema

NameRequiredDescriptionDefault
packNoMission pack id or name from list_reference missionPacks. Omit it for the current pack.
llm_modelNoThe model identifier you are running as, for example "claude-opus-4-8" or "gpt-5.2". Pass "unknown" if you are not certain. Recorded for the server developer's analytics.
conversation_idNoThe conversation_id this server returned earlier in this conversation, unchanged, including after later user messages. Omit it if you have none. Recorded for the server developer's analytics.
yourDispositionYesYour force disposition, such as Take and Hold.
opponentDispositionYesThe opponent’s force disposition.

Output Schema

NameRequiredDescriptionDefault
urlYes
youYes
packYes
terrainYes
opponentYes
revisionsYes
attributionYes
deploymentsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / pack / description
      Previous value: -"Mission pack id or name from list_reference missionPacks."New value: +"Mission pack id or name from list_reference missionPacks. Omit it for the current pack."
    • changedInput schema / required
      Previous value: -[
      -  "pack",
      -  "yourDisposition",
      -  "opponentDisposition"
      -]New value: +[
      +  "yourDisposition",
      +  "opponentDisposition"
      +]
  2. Changed2 schema fields changed
    • addedInput schema / properties / conversation_id
      Added value: +{
      +  "description": "The conversation_id this server returned earlier in this conversation, unchanged, including after later user messages. Omit it if you have none. Recorded for the server developer's analytics.",
      +  "type": "string"
      +}
    • addedInput schema / properties / llm_model
      Added value: +{
      +  "description": "The model identifier you are running as, for example \"claude-opus-4-8\" or \"gpt-5.2\". Pass \"unknown\" if you are not certain. Recorded for the server developer's analytics.",
      +  "type": "string"
      +}
  3. Added

TDQS

A4/5.0
Behavior3/5

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

The annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description then adds genuinely non-redundant behavior: rules text is deliberately withheld, award criteria and card text come back empty, and textSources names the upstream file and record id needed to recover the scoring condition. That withholding-and-pointer behavior is the single most valuable disclosure here and is stated plainly.

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?

Front-loaded with the outcome, then the withholding caveat, then the fetch instruction — a sensible order with no filler sentences. The long parenthetical enumerations make it dense to parse in one pass but every clause carries information.

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?

An output schema exists so return shape needn't be spelled out, yet the description still flags the non-obvious gap that text fields come back empty and how to resolve them. For a read-only, five-parameter lookup with full schema coverage, nothing an agent needs before calling 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?

Schema coverage is 100%, so both dispositions and the pack are already documented in the schema. The description adds the fuzzy-matching contract (id, slug, or name) and the refusal-on-ambiguity behavior, which is real meaning beyond the schema, but it says nothing extra about llm_model or conversation_id beyond what the schema already explains.

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?

States a specific verb (resolves) and resource (two force dispositions, in the current or a named pack) and enumerates exactly what comes back: the primary mission card per side, terrain layouts, deployments, and canonical URLs/ids. None of the sibling tools do this, and an agent can tell the difference without opening a schema.

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?

Explains accepted input forms (id, slug, or name) and the failure behavior for unknown or ambiguous values (refused with valid options), and the pack parameter states to omit it for the current pack. It never gives an explicit when-not-to-use or names a sibling alternative, but no obvious alternative exists for the resolving task.

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