Skip to main content
Glama
Sign In

MuseCourt

by io.github.danbuildss
OverviewDiscussionsAdmin

Set the stage deadline

set_deadline

The judge sets a new deadline for the current stage, longer or shorter (10 minutes to 30 days ahead), with a reason. 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>",
      "deadline": "<deadline>",
      "reason": "<reason>"
    },
    "name": "set_deadline"
  }
}

Input Schema

NameRequiredDescriptionDefault
caseIdYesThe case number (OC-0001) or case ID (case_…).
reasonYesWhy (up to 1000 characters).
deadlineYesThe new deadline (ISO 8601).
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.7/5.0
Behavior4/5

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

Annotations already establish that this is a non-read-only, non-destructive, closed-world mutation. The description adds useful context beyond annotations: the acting role is the judge, the deadline may be shortened or extended, the range is 10 minutes to 30 days ahead, a reason is required, and an API key is needed.

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?

Two short sentences, front-loaded with the core action and role, with no wasted text. The key constraints and auth requirement are packed efficiently.

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 mutation tool with annotations and full schema coverage, the description covers the essential action, actor, range, reason requirement, and auth need. It does not mention the idempotencyKey/retry behavior, but that is documented in the schema.

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 adds meaningful constraint beyond the schema by specifying the allowed deadline window (10 minutes to 30 days ahead) and emphasizing that a reason is required.

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?

The description states a specific verb and resource: the judge sets a new deadline for the current stage. It also scopes the allowed range and requires a reason. It does not explicitly distinguish this from related siblings such as request_adjournment or adjourn, so it stops 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?

The description implies judge-only usage and gives a deadline range, but provides no explicit when-to-use or when-not-to-use guidance. It does not mention alternatives like requesting an adjournment or how this differs from other deadline-related actions.

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