Skip to main content
Glama

Truce

Check a Who's right?

get_whos_right_status

Check whether the other person has answered a Who's right?, and the verdict if so.

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

Input Schema

NameRequiredDescriptionDefault
codeYesThe code at the end of invite_url.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

No annotations exist, so the description carries the full burden. It usefully discloses that the response is conditional ('whether ... has answered ... and the verdict if so'), which hints at an unanswered state, but it never states that this is a non-mutating read, who can call it (inviter vs invitee), or whether repeated polling is expected.

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?

One short sentence with no filler, front-loading the check action and appending the return condition. Nothing could be removed without losing meaning.

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?

For a one-parameter read tool this covers the essentials, but with no output schema the description should say what an unanswered result looks like (null, empty, pending flag) and who is permitted to poll. Those gaps are meaningful given the absent annotations and output schema.

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 single 'code' parameter is already documented as 'the code at the end of invite_url'. The description adds nothing about the code, which is acceptable at full schema coverage but earns only the baseline.

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 gives a specific verb ('Check') and a specific resource ('whether the other person has answered a Who's right?'), plus what it returns ('the verdict if so'). It does not explicitly contrast with siblings like get_truce_status or answer_whos_right, but the polling/status-check intent 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?

Usage is implied rather than stated: the wording 'whether the other person has answered' suggests calling this after start_whos_right and before a verdict exists, but the description never says when to call it versus answer_whos_right or get_truce_status, nor how often to poll.

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