Skip to main content
Glama

court_closing

Runs a closing hearing over grouped round losses to consolidate failed rounds and produce a final adversarial verdict for AI coding agent submissions.

Instructions

Step 4: Run closing hearing over grouped round losses.

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": {
      "round_dir": "<round_dir>",
      "brief_path": "<brief_path>",
      "law_dir": "<law_dir>"
    },
    "name": "court_closing"
  }
}

Input Schema

NameRequiredDescriptionDefault
modelNo
law_dirYes
providerNo
cache_dirNo
round_dirYes
brief_pathYes
budget_usdNo
ledger_pathNo
tracker_pathNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.3/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. It does not disclose whether this writes files, requires specific permissions, consumes budget, or has side effects, despite parameters like budget_usd, ledger_path, and cache_dir strongly suggesting consequential behavior.

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 filler, but its brevity crosses into under-specification. It is concise without being clarifying.

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 a nine-parameter tool with no annotations, no output schema, and zero schema description coverage, the description is far too sparse to explain safe invocation. It does not compensate for any of the missing structured context.

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 nine parameters, and the description does not explain any of them, including required parameters round_dir, brief_path, and law_dir. It provides no meaning beyond the bare parameter names.

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 names an action ("Run closing hearing") and a target ("grouped round losses"), but "closing hearing" is unexplained jargon and the description does not distinguish this tool from siblings such as court_judge or court_trial_round. It signals this is a later step in a process but leaves the actual operation vague.

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?

The phrase "Step 4" implies ordering in a workflow, which is some usage guidance. However, it gives no explicit conditions for when to call this tool, no prerequisites, and no routing guidance relative to the sibling tools.

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