Skip to main content
Glama

court_judge

Judges a plan against challenges and rebuttals and records verdict and precedents to support adversarial review of AI coding plans.

Instructions

Step 1: Judge a plan against challenges and rebuttals, recording verdict and precedents.

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": {
      "plan_path": "<plan_path>",
      "rebuttal_path": "<rebuttal_path>",
      "challenge_path": "<challenge_path>",
      "law_dir": "<law_dir>"
    },
    "name": "court_judge"
  }
}

Input Schema

NameRequiredDescriptionDefault
modelNo
law_dirYes
out_pathNo
providerNo
cache_dirNo
plan_pathYes
budget_usdNo
ledger_pathNo
rebuttal_pathYes
challenge_pathYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.4/5.0
Behavior2/5

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

With no annotations, the description carries the full burden, yet it only hints at a write ('recording verdict and precedents') without saying where output goes, whether it is persisted or reversible, or what permissions are needed. The presence of budget_usd and ledger_path in the schema implies cost tracking and accounting side effects that the description never mentions.

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?

It is a single front-loaded sentence with no filler. The 'Step 1' prefix is arguably wasted or confusing wording, but the text is otherwise tight.

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

Completeness2/5

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

For a 10-parameter tool with zero schema documentation, no annotations, and no output schema, one sentence is far too thin. An agent would not know what the tool writes, what units budget_usd takes, or how law_dir and out_path interact.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% across 10 parameters, so the description must compensate and largely does not. It only loosely implies the roles of plan_path, challenge_path, and rebuttal_path, while law_dir, out_path, cache_dir, ledger_path, budget_usd, model, and provider are left entirely unexplained.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description gives a specific verb ('Judge') and object ('a plan against challenges and rebuttals') plus a stated side effect ('recording verdict and precedents'). However, the 'Step 1' prefix and the court metaphor leave the actual operation partly vague, and it does not explicitly distinguish itself from siblings like court_trial_round or court_verify_evidence.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

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

'Step 1' weakly signals a position in a sequence, which is the only usage hint. There is no statement of when to call this versus court_trial_round, court_closing, or court_replay_gate, and no prerequisites or exclusions are given.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.