Skip to main content
Glama

court_challenge

Submit a plan (JSON, Markdown, or YAML) to Prosecutor and Public Defender agents for adversarial review, exposing risks and counterarguments before implementation.

Instructions

Step 1: Challenge a plan (.json/.md/.yaml) with Prosecutor and Public Defender.

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>",
      "law_dir": "<law_dir>"
    },
    "name": "court_challenge"
  }
}

Input Schema

NameRequiredDescriptionDefault
modelNo
law_dirYes
out_pathNo
providerNo
cache_dirNo
plan_pathYes
budget_usdNo
ledger_pathNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

D1.9/5.0
Behavior1/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It does not state whether the tool is read-only or mutating, what side effects occur, what permissions are needed, how budget or caching parameters affect execution, or what the tool returns.

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

Conciseness3/5

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

The description is a single front-loaded sentence with no wasted words, which is structurally efficient. However, its brevity reflects under-specification rather than disciplined conciseness, given the tool's complexity.

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

Completeness1/5

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

For an 8-parameter tool with no annotations, no output schema, and 0% schema description coverage, the description is far too sparse. It does not explain parameter meanings, execution behavior, workflow context, or expected outcomes, leaving an agent unable to invoke the tool correctly.

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

Parameters1/5

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

Schema description coverage is 0% across 8 parameters, and the description only indirectly references plan_path by mentioning plan file formats. Required parameters like law_dir and optional parameters such as model, provider, cache_dir, out_path, budget_usd, and ledger_path are left completely 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 states a specific verb ('Challenge') and resource ('a plan') and lists accepted file formats, so the basic action is identifiable. However, 'with Prosecutor and Public Defender' is metaphorical and does not clarify what challenging actually entails or how it differs from sibling tools like court_trial_round or court_judge.

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' implies this is the first action in a workflow, giving minimal usage context. There is no explicit guidance on when to use this tool versus alternatives, no prerequisites beyond the required parameters, and no when-not-to-use conditions.

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