Skip to main content
Glama

Truce

Read a Truce invite

get_invite

For the agent of someone who received a Truce invite link (trucehq.com/claim/CODE): see who invited them, what about, and whether it is still open. Read-only.

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_invite"
  }
}

Input Schema

NameRequiredDescriptionDefault
codeYesThe code at the end of the invite link.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does useful work: 'Read-only' substitutes for a readOnlyHint, and it enumerates the returned facts including whether the invite is still open. It says nothing about authorization requirements, what an invalid or expired code produces, or any rate limiting.

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 sentences, zero filler. The audience and purpose are front-loaded, with the read-only safety note last, which is exactly the right ordering for an agent scanning for fit.

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 single-parameter read with no output schema, the description supplies the return content and a safety profile, which is nearly everything needed to call it correctly. The remaining gap is failure behavior for invalid or already-claimed codes.

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 code parameter is already described as 'The code at the end of the invite link.' The description's trucehq.com/claim/CODE example corroborates that but adds no new syntax, validation, or format detail beyond the schema.

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 names a specific read operation ('see who invited them, what about, and whether it is still open') and frames it for a distinct audience — the agent of an invite recipient, versus the initiator-facing siblings like start_truce. It does not explicitly name a sibling it is not, so it stops short of a 5.

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?

The 'For the agent of someone who received a Truce invite link' framing gives a clear triggering condition, and the parenthetical URL pattern tells the agent where the code comes from. It offers no exclusion or routing advice, though — it never says to use answer_truce once the agent wants to respond to the invite.

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