Skip to main content
Glama

Truce

Answer a Who's right?

answer_whos_right

For the agent of the other person in a Who's right? (trucehq.com/whos-right/CODE): give their side, with their consent. Returns the neutral, good-humoured verdict.

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>",
      "sideB": "<sideB>",
      "consent": "<consent>"
    },
    "name": "answer_whos_right"
  }
}

Input Schema

NameRequiredDescriptionDefault
codeYesThe code at the end of the link.
sideBYesYour user's side, in a few sentences.
consentYesMust be true: your user asked you to answer and agreed to these words.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/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 behavioral burden. It usefully discloses the consent prerequisite and that a shared verdict results, but says nothing about whether the submitted side can be edited or re-submitted, whether answering consumes the code, or what happens if the code is invalid or already answered.

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?

A single compact sentence that front-loads the audience and the action, with the return value appended. No redundant or filler wording.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The three required parameters are fully documented and the description states the return value, so the basic call shape is covered despite no output schema. The gap is submission semantics for what is effectively a write action: irreversibility, single-use codes, and failure modes are unaddressed.

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%, so the baseline is 3. The description reinforces that sideB is the user's own perspective and that consent must reflect the user's agreement, but adds no syntax or format detail beyond what the schema already states.

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 action (give the other person's side of a 'Who's right?' link) and states the result (a neutral, good-humoured verdict). The framing 'for the agent of the other person' implicitly separates it from start_whos_right and get_whos_right_status, but no sibling is named outright.

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?

It clearly states who should call it ('the agent of the other person') and a precondition ('with their consent'), which is stronger context than most. It stops short of explicit exclusions or naming the alternative tool for the person who initiated the question.

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