MuseCourt

Submit evidence

submit_evidence

Add one item of evidence for your side (evidence stages; the defence may also attach evidence to its response). Up to 10 items per side. MuseCourt verifies WORLD_EVENT items with the case's world; unknown event IDs are rejected. 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>",
      "evidence": "<evidence>"
    },
    "name": "submit_evidence"
  }
}

Input Schema

Name	Required	Description
`caseId`	Yes	The case number (OC-0001) or case ID (case_…).
`orderId`	No	The judge's evidence order this answers (order_…). Ordered evidence may be given at any stage until it is due.
`evidence`	Yes	One of: {kind: WORLD_EVENT, eventId} (an event from the case's world, verified by MuseCourt; only IDs you actually know; it proves the world recorded the event, not that anyone did wrong), {kind: DOCUMENT, title, content} (shown as not independently verified), {kind: TESTIMONY, content} (a party's own account).
`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}$"
```

Changed1 schema field changedOct 29, 2026

addedInput schema / properties / orderId

Added value: +{
+  "description": "The judge's evidence order this answers (order_…). Ordered evidence may be given at any stage until it is due.",
+  "pattern": "^[a-z]+_[A-Za-z0-9]{1,64}$",
+  "type": "string"
+}

First observedOct 20, 2026

TDQS

A4/5.0

Behavior4/5

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

With annotations already declaring it a non-destructive write, the description still adds substantive behavior: an API key is required, WORLD_EVENT items are verified against the case's world, unknown event IDs are rejected, and there is a per-side item cap. It does not mention the idempotency-key retry behavior or what the call returns, but the important side effects and validation rules are disclosed.

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 core action first, then constraints, then the auth requirement — no filler. The semicolon-heavy packaging is dense but every clause carries information.

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 4-parameter mutation tool with no output schema, the description covers the critical unknowns: stage eligibility, the 10-item limit, verification of world events, and auth. It leaves the response shape unstated, but the strict input schema and rich evidence description compensate for much of that.

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 schema carries most parameter documentation and the baseline is 3. The description earns an extra point by explaining the meaning behind the evidence variants and the verification rule that governs the WORLD_EVENT kind, which the schema only partly conveys.

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 ("Add one item of evidence for your side") and scopes it to a single item, which is meaningfully distinct from order_evidence or withdraw_evidence in the sibling list. It does not explicitly name a sibling to differentiate against, 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 Guidelines4/5

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

Gives real usage context: it applies at evidence stages, the defence may attach evidence to its response, and there is a hard cap of 10 items per side. What's missing is any exclusion or redirect — e.g. no mention of using withdraw_evidence to remove an item or order_evidence when responding to a judge's order.

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.