Skip to main content
Glama

Truce

Answer a Truce

answer_truce

For the agent of the invited person: give their side of the Truce, in private, so the neutral mediator can propose something fair. Only with their explicit consent to the exact words. They still read the proposal and sign themselves.

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": "<name>",
      "statement": "<statement>",
      "wants": "<wants>",
      "consent": "<consent>"
    },
    "name": "answer_truce"
  }
}

Input Schema

NameRequiredDescriptionDefault
codeYesThe code at the end of the invite link.
nameYesYour user's first name.
emailNoOptional: your user's email for updates.
floorNoOptional, private: the least your user could accept. Never shown to the other side.
wantsYesWhat your user would like to happen.
consentYesMust be true: your user asked you to answer and agreed to these words.
statementYesYour user's side, in their words.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

With no annotations, the description carries real weight and does so: it discloses that the submission is private, that a neutral mediator will act on it, that the invitee still reviews and signs the proposal themselves, and that consent must match the exact wording. Missing only mechanics like what happens if consent is false or how the statement is later surfaced.

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?

Three short sentences, actor and scope front-loaded, then the consent constraint, then the downstream flow. No filler and nothing buried.

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 7-parameter, 5-required write tool with no annotations and no output schema, the description supplies the missing behavioral context: privacy, consent, mediator role, and the counterpart's own signing step. Only minor gaps remain around failure behavior and confirmation of what the caller gets back.

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 every parameter is already documented. The description reinforces the meaning of 'consent' (agreed to these words) and the private nature of the input, but adds no format, length, or validation detail beyond the schema. 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?

Opens with a specific actor plus verb plus resource: 'For the agent of the invited person: give their side of the Truce'. The invited-person framing implicitly distinguishes it from start_truce and the status readers, though no sibling is named explicitly, so it falls short of a clean 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?

Clear context for use — you are acting for the invited party, you need their explicit consent to the exact words, and the counterpart flow (mediator proposes, they read and sign) is described. It does not spell out when not to use it or name an alternative tool, so not a 5.

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