Skip to main content
Glama

Truce

Start a Who's right?

start_whos_right

Start a free, friendly 'Who's right?' for a light everyday argument. Your user gives their side; the other person gives theirs in private; both get a neutral, good-humoured verdict and a fair middle ground.

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>",
      "nameA": "<nameA>",
      "nameB": "<nameB>",
      "sideA": "<sideA>"
    },
    "name": "start_whos_right"
  }
}

Input Schema

NameRequiredDescriptionDefault
emailNoOptional: your user's email.
nameAYesYour user's first name.
nameBYesThe other person's first name.
sideAYesYour user's side, in a few sentences.
topicYesWhat the argument is about.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full burden. It discloses the flow (user submits a side now, the other person answers privately, both receive a verdict and middle ground) and that the service is free, which is genuinely useful. However, it never says what the call returns or how the other party is reached (there is a get_invite sibling, suggesting an invite step), leaving the agent unsure what to do after invoking it.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, front-loaded with the action and followed by the workflow; no sentence is wasted. The adjectives "free, friendly" and "neutral, good-humoured" are light marketing but do set expectations about tone, so they mostly earn their place.

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 five-parameter tool with no annotations and no output schema, the description covers the workflow but not the response. An agent still cannot tell whether it receives an invite link, a case id, or a status to poll, nor whether it must follow up with another tool.

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 all five parameters are already documented, and the baseline is 3. The description does add real meaning by clarifying that only the user's side (sideA) is collected at this step while the other person's side arrives privately later, but it adds nothing about email, topic format, or name usage 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?

States a specific verb and named resource ("Start a ... 'Who's right?'") plus the scenario it serves, so an agent can tell it apart from answer_whos_right or get_whos_right_status. It stops short of explicitly naming the sibling it is not, so a 4 rather than 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 Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

"For a light everyday argument" gives an implied usage context and effectively signals when not to use it (heavy disputes), but that boundary is never stated outright and no alternative tool is named. Usage must be inferred rather than read.

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