Skip to main content
Glama

Truce

Start a Truce

start_truce

Start a Truce (neutral, private mediation) for your user about a real disagreement. Returns an invite link for your user to send to the other person, and a private link for your user. Free unless money is involved.

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": {
      "topic": "<topic>",
      "name": "<name>",
      "statement": "<statement>",
      "wants": "<wants>"
    },
    "name": "start_truce"
  }
}

Input Schema

NameRequiredDescriptionDefault
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.
oliveNoOptional short, kind note to the other person.
topicYesWhat the disagreement is about, in a few neutral words.
wantsYesWhat your user would like to happen.
categoryNoOptional: deposit, invoice, flatmates, neighbours, friends, business, family or other.
otherNameNoThe other person's first name.
statementYesYour user's side, in their words.

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 no annotations, the description carries the full load and does well: it discloses what is returned (an invite link plus a private link), that the process is neutral and private, and that the service is free unless money is involved. It stops short of explaining side effects such as whether the other party is notified or what happens after the invite is sent, so it is strong but not complete.

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 with no filler; the core purpose is front-loaded and the return/cost facts follow immediately. Every clause earns its place.

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 9-parameter tool with no output schema, the description usefully covers the return values and the privacy/cost model. The remaining gap is process transparency — whether an invite is sent automatically, how the other person is reached, and what the private link is for — which matters for a mediation workflow.

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 description coverage is 100%, including the sensitive 'floor' parameter being marked private and never shown to the other side, so the schema already does the semantic work. The description adds no parameter-level meaning beyond that, which is the expected baseline when the schema is this rich.

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 ('Start a Truce') and clarifies it as 'neutral, private mediation ... about a real disagreement', which distinguishes it in spirit from the adversarial-sounding start_whos_right. It never names a sibling explicitly, so an agent must still infer the routing, but the purpose itself is unmistakable.

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 'for your user about a real disagreement' implies a usage context, and 'Free unless money is involved' hints at a cost caveat. There is no explicit when-to-use-vs-alternative statement, no exclusion (e.g. when a simple answer would do instead), and no prerequisites such as needing the other person's contact info.

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