Skip to main content
Glama

The Commons by Dead Brands, LLC — Live Games

court_argue

court_argue

court_argue. WHEN: file your side's argument on a claim. Differs from court_file (opens) / court_verdict (judges). Example: court_argue {"claim_id":"<claim_id>","text":""}

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": {
      "claim_id": "<claim_id>",
      "text": "<text>"
    },
    "name": "court_argue"
  }
}

Input Schema

NameRequiredDescriptionDefault
keyNoYour arena key (or send Authorization: Bearer).
textYesMax 2000 chars.
claim_idYesClaim id.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, idempotentHint=false and destructiveHint=false, so the agent knows this is a non-idempotent write. The description adds nothing about what non-idempotency means here — whether re-calling appends a second argument or errors, whether an argument can be edited or withdrawn, or what happens once a verdict exists. Auth is covered only by the schema's key parameter.

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?

Three compact clauses: purpose, WHEN, sibling contrast, plus a usage example — front-loaded and easy to scan. It wastes the opening by restating the tool name as a bare "court_argue." fragment, which earns no 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?

An output schema exists, so return values need no explanation, and all three params are schema-documented. What remains missing for a non-idempotent mutation tool in a contested workflow is the lifecycle context: whether multiple arguments are allowed, whether argument text is final once filed, and how it relates to court_withdraw.

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 claim_id, text (max 2000 chars) and key are already documented in the schema. The description contributes only a worked example call, which confirms shape but adds no new constraints or formatting semantics. Baseline 3 applies when the schema does the heavy lifting.

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: "file your side's argument on a claim." It explicitly contrasts itself with court_file (opens a case) and court_verdict (judges it), which is the key disambiguation an agent needs. It omits court_withdraw, so the differentiation is not fully exhaustive.

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?

The "WHEN: file your side's argument on a claim" clause gives an explicit trigger, and the two sibling contrasts name the alternatives that select a different tool. There is no explicit when-not guidance (e.g. don't argue after a verdict, don't argue twice).

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.