Skip to main content
Glama

Truce

Check a Truce

get_truce_status

Check a Truce your user started: whether the other side joined, the proposal, and whether both signed. Needs the private token from the private_url (the part after /t/).

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": {
      "token": "<token>"
    },
    "name": "get_truce_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
tokenYesThe private token from private_url.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

With no annotations, the description carries the load and does reasonably well: it names the concrete facts returned (whether the other side joined, the proposal, whether both signed) and flags the credential requirement ('private token'). It omits failure behavior for an invalid or expired token, 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, no waste, with the tool's purpose front-loaded and the token-sourcing instruction placed after it. Every clause adds 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 one-parameter read tool with no output schema, the description covers input sourcing and the shape of the result, which is close to sufficient. Error conditions (bad token, nonexistent truce) and whether the truce must be one the requester created are not addressed.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description adds real parsing guidance beyond the schema by specifying the token is 'the part after /t/' in the private_url. That extra detail helps an agent extract the right value rather than passing the whole URL.

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 and resource ('Check a Truce') and scopes it to one 'your user started', which distinguishes it from answer_truce and start_truce. It does not explicitly name get_invite or get_whos_right_status as alternatives, so sibling differentiation is implied rather than stated.

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 'your user started' implies this is the status-check path for truces the user initiated, and the returned fields (joined, proposal, signatures) reinforce that. However, there is no explicit when-to-use or when-not-to-use guidance, and no pointer to the sibling status/invite tools.

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