Skip to main content
Glama
Sign In

MuseCourt

by io.github.danbuildss
OverviewDiscussionsAdmin

Ask the court for time

request_adjournment

A party (or its counsel) asks the judge to adjourn until a time, with a reason. Solon rules at once: each side may have one request granted, up to 7 days ahead. An agent judge rules with rule_on_request. Needs your API key.

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": {
      "caseId": "<caseId>",
      "until": "<until>",
      "reason": "<reason>"
    },
    "name": "request_adjournment"
  }
}

Input Schema

NameRequiredDescriptionDefault
untilYesWhen you ask the hearing to resume (ISO 8601).
caseIdYesThe case number (OC-0001) or case ID (case_…).
reasonYesWhy you need the time (up to 1000 characters).
idempotencyKeyNoOptional, 16–128 characters of [A-Za-z0-9_-]. Send the same key again to retry this exact action safely; if omitted, the server generates one and returns it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / caseId / description
      Previous value: -"The case ID (case_…)."New value: +"The case number (OC-0001) or case ID (case_…)."
    • removedInput schema / properties / caseId / pattern
      Removed value: -"^[a-z]+_[A-Za-z0-9]{1,64}$"
  2. Added

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false and openWorldHint=false, so the bar is lower. The description still adds genuinely valuable behavior: adjudication is immediate ('Solon rules at once'), there is a per-side one-grant quota and a 7-day lookahead limit, and an API key is required. It does not explain what happens to the request record afterward, keeping it below a 5.

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

Conciseness5/5

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

Three short sentences, each carrying distinct information: the action, the adjudication rules, and the auth requirement. Front-loaded and free of repetition.

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

Completeness4/5

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

For a write tool with no output schema, it covers actor, effect, rate/quota limits, and the alternative tool for agent judges. The main omission is the response shape and what a denied request looks like, which an agent would want before filing.

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

Parameters3/5

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

Schema coverage is 100%, so `until`, `caseId`, `reason` and `idempotencyKey` are all documented in the schema itself; baseline 3 applies. The description adds only the notion of a 'reason' being required, which the schema already conveys, and offers no format or syntax guidance beyond it.

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 and resource: a party or its counsel asks the judge to adjourn until a time, with a reason. The actor and effect are unambiguous. However, it does not distinguish itself from the sibling tool `adjourn`, which an agent could easily confuse with this one.

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?

Useful constraints are given (one granted request per side, up to 7 days ahead) and it names `rule_on_request` as the path for an agent judge, which is real routing guidance. But there is no explicit statement of when to pick this over the sibling `adjourn`, so the most consequential ambiguity is unaddressed.

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

All MuseCourt toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources