Skip to main content
Glama
Sign In

MuseCourt

by io.github.danbuildss
OverviewDiscussionsAdmin

Withdraw a case

withdraw_case

The plaintiff side withdraws the case, giving a reason. It closes without a verdict. 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>",
      "reason": "<reason>"
    },
    "name": "withdraw_case"
  }
}

Input Schema

NameRequiredDescriptionDefault
caseIdYesThe case number (OC-0001) or case ID (case_…).
reasonYesWhy (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. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Adds real behavioral context beyond the annotations: the case terminates without a verdict, the call is restricted to the plaintiff side, and an API key is required. It does not cover failure modes or what the response contains, and the idempotencyKey retry story is left entirely to the schema.

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 short sentences with the effect ('closes without a verdict') front-loaded right after the action. 'Needs your API key' is mildly boilerplate but earns a small place as an auth cue.

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

Completeness3/5

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

A mutation tool with no output schema and no annotations describing side effects; the description covers the state change but says nothing about what is returned, permission errors, or whether withdrawal can be undone. Adequate, but a gap remains for an irreversible case-closing action.

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 description coverage is 100%, so the schema already explains caseId formats, the reason field, and the idempotencyKey retry semantics. The description only adds that a reason is required, which the schema's required list already conveys; baseline 3 applies.

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 (withdraws) and resource (the case) plus the acting party (plaintiff side) and the outcome (closes without a verdict). This implicitly separates it from withdraw_as_counsel, withdraw_evidence, withdraw_settlement_offer and dismiss_case, though no sibling is named explicitly.

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?

Usage is implied by 'the plaintiff side withdraws the case' and the requirement to give a reason, so an agent can infer when it applies. There is no explicit when-not guidance or routing to the adjacent tools (dismiss_case, withdraw_as_counsel) that could be confused with it.

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