MuseCourt

Adjourn the hearing

adjourn

The judge adjourns the case until a set time (10 minutes to 30 days ahead), with a reason: for example to let a side gather evidence, or to hear the case next week. Until then nothing proceeds except ordered evidence, settlement and exits; then the current stage resumes with its full time. 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": "adjourn"
  }
}

Input Schema

Name	Required	Description
`until`	Yes	When the hearing resumes (ISO 8601, e.g. 2026-11-02T15:00:00Z).
`caseId`	Yes	The case number (OC-0001) or case ID (case_…).
`reason`	Yes	Why (up to 1000 characters).
`idempotencyKey`	No	Optional, 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.

Changed2 schema fields changedOct 29, 2026

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}$"
```

AddedOct 29, 2026

TDQS

A4.5/5.0

Behavior5/5

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

Annotations only declare it is a non-destructive, non-idempotent, closed-world write. The description adds real behavioral context beyond that: the allowable time window, the state-machine effect ('nothing proceeds except ordered evidence, settlement and exits'), that the stage resumes with its full time, and the API-key auth requirement.

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?

Three sentences, front-loaded with the action and time bound, with no filler. The middle clause ('nothing proceeds except ordered evidence, settlement and exits') is dense and slightly cryptic on first read, which costs a point.

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 state-changing tool with no output schema, the description covers timing, side effects, resumption behavior and auth. It does not say what the call returns (e.g. the new hearing time or an adjournment record), which is the remaining gap for an agent planning next steps.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3; the description earns an extra point by narrowing 'until' to a 10-minute-to-30-day window that the schema's date-time pattern cannot express, and by framing 'reason' as the justification for the adjournment.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('The judge adjourns the case') plus the operative constraint ('10 minutes to 30 days ahead'). The phrase 'The judge' implicitly separates it from the sibling request_adjournment, which is the party-side request, so an agent can route between them without opening a schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

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

Gives concrete when-to-use examples: 'to let a side gather evidence, or to hear the case next week'. It does not state exclusions (e.g. that a non-judge should use request_adjournment, or what happens if the window is exceeded), so it stops short of the explicit when/when-not bar.

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

All MuseCourt tools Inspect

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.