Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

No arguments

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
court_verify_evidenceC

Bailiff deterministic verification for verbatim quotes, AST citations, or command exhibits.

court_assemble_lawC

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

court_challengeD

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

court_judgeC

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

court_replay_gateD

Step 3a: Zero-cost replay gate and blast-radius boundary verification.

court_trial_roundC

Step 3c: Run evaluation trials across sample artifacts with Bailiff fact-checking.

court_closingC

Step 4: Run closing hearing over grouped round losses.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

C2.7/5.0

Scored across 7 tools

Disambiguation4/5

Each tool maps to a distinct courtroom phase (assembly, challenge, judging, replay gate, trial rounds, closing, evidence verification), and the explicit step labels (Step 1, 3a, 3c, 4) help order them. Minor overlap exists between court_trial_round and court_closing, which both evaluate losses, and between court_challenge and court_judge as sequential Step 1 actions, but their roles are separable.

Naming Consistency4/5

All seven tools share the court_ prefix, which makes the family instantly recognizable and scannable. The suffixes mix verb forms (challenge, judge, assemble_law, verify_evidence) with noun forms (replay_gate, trial_round, closing), a small deviation but still predictable within the courtroom metaphor.

Tool Count5/5

Seven tools for a multi-stage trial pipeline is well-scoped; each tool corresponds to a stage in the process rather than a redundant variant. Nothing feels padded, and the set stays small enough to be navigable.

Completeness3/5

The surface covers assembly, challenge, judgment, gating, trials, closing, and evidence checks, but the step numbering (1, 3a, 3c, 4) implies missing operations such as a rebuttal/Step 2 and a Step 3b phase. There are also no read/query tools to retrieve prior verdicts, precedents, or cases, only tools that record or run them, leaving agents without inspection paths.

Maintenance

ActivityMaintained
ResponsivenessNo recent community issues