Skip to main content
Glama

court_assemble_law

Assembles hierarchical Parts 0-3 Law from a specified directory, combining Owner Decisions, Case Law, ENABLED Rules, and Conventions for courtroom use.

Instructions

Assemble hierarchical Parts 0-3 Law (Owner Decisions, Case Law, ENABLED Rules, Conventions).

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

Input Schema

NameRequiredDescriptionDefault
law_dirYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.6/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 behavioral burden and does not meet it. It never says whether this writes files to disk, overwrites or merges existing output, whether it is idempotent, or what it returns; 'assemble' alone leaves the mutation profile ambiguous.

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?

One compact sentence with the action and the constituent categories front-loaded and no filler wording. Its brevity is efficient rather than padded, though the parenthetical list is terse enough to be ambiguous about whether those are inputs or outputs.

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?

With no annotations, no output schema, and an undocumented required parameter, the description leaves the two things an agent most needs — where law_dir points and what artifact is produced — entirely unstated. For a tool that appears to build and persist a hierarchy of legal documents, this is insufficient.

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% and the single parameter law_dir is never mentioned in the description. An agent must guess whether it is an input source directory, the output destination, or a root containing the four categories — meaning the description adds nothing beyond the bare property name.

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 ('Assemble') and a specific artifact ('hierarchical Parts 0-3 Law'), then enumerates the four input categories it composes (Owner Decisions, Case Law, ENABLED Rules, Conventions). The term 'Parts 0-3 Law' is domain jargon that an outside agent may not fully decode, and no sibling (e.g. court_verify_evidence, court_judge) is referenced for contrast, so it falls short of 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 Guidelines2/5

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

There is no statement of when this should be invoked, no preconditions (e.g. that the source categories must already exist), and no mention of alternatives among the court_* siblings. The only hint at usage is the implicit notion that assembling a law bundle is a distinct step, which is inference rather than guidance.

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