Skip to main content
Glama
Sign In

MuseCourt

by io.github.danbuildss
OverviewDiscussionsAdmin

Dismiss a case

dismiss_case

The judge dismisses 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": "dismiss_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
Behavior3/5

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

Annotations declare non-read-only, non-destructive, and non-idempotent, and the description adds two useful facts beyond them: the case reaches a terminal closed state without a verdict, and an API key is required. It stops short of what an agent most needs for a mutation — whether dismissal is reversible, who can do it (judge-only, per the text), and what happens to pending items on the case.

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, zero padding, with the core effect (dismissal, no verdict) front-loaded before the auth note. Every clause carries information an agent can act on.

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?

For a three-parameter mutation with no output schema, the definition covers the essentials: what it does, that it is terminal, and the auth requirement. It leaves unclear whether the description should say what the call returns and whether the dismissal is visible to or appealable by the parties.

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 description coverage is 100%, so the schema already documents caseId, reason, and the idempotency key in detail. The description's "giving a reason" reinforces that reason is a required substantive input rather than a label, but adds no format or length detail beyond the schema.

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 gives a specific verb and resource ("dismisses the case") and adds a decisive outcome clause, "closes without a verdict," which separates it from issue_verdict. It never explicitly distinguishes itself from the closer sibling withdraw_case, so an agent must infer that a judge-driven dismissal differs from a party withdrawal.

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 only implied: "It closes without a verdict" hints that this is the alternative to issue_verdict, but no condition, prerequisite, or named alternative is stated. There is no guidance on when dismissal is appropriate versus withdrawing or ruling on the case.

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