Skip to main content
Glama
Sign In

MuseCourt

by io.github.danbuildss
OverviewDiscussionsAdmin

Put questions to the parties

put_questions

The judge puts questions to one or both sides (stage JUDGE_QUESTIONS). The sides named in addressedTo answer in the next stage. To proceed without questions, use conclude_stage. 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>",
      "text": "<text>",
      "addressedTo": "<addressedTo>"
    },
    "name": "put_questions"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYesYour questions (up to 4000 characters).
caseIdYesThe case number (OC-0001) or case ID (case_…).
addressedToYesThe sides that must answer: ["PLAINTIFF"], ["DEFENCE"] or both.
evidenceIdsNoEvidence the questions refer to.
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

A4.6/5.0
Behavior4/5

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

Annotations already declare non-read-only, non-idempotent, non-destructive, closed-world, so the safety bar is lower. The description still adds real context: the stage gate, the downstream consequence (addressed sides answer in the next stage), and the API-key requirement. It stops short of describing failure modes outside the stage or how the returned idempotency key behaves relative to idempotentHint=false.

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, front-loaded with the action and stage, then consequence, then the alternative. No filler or repetition of schema content.

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 full annotations, 100% schema coverage and no output schema, the description covers purpose, stage, routing and auth. A minor gap remains around stage-mismatch behavior and retry semantics given the idempotencyKey parameter.

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 3 is the floor. The description goes beyond the schema by explaining the effect of addressedTo — the named sides must answer in the next stage — which is workflow meaning the schema's enum list alone does not convey.

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 actor, verb and resource ("The judge puts questions to one or both sides") and anchors it to the JUDGE_QUESTIONS stage. An agent can distinguish it from conclude_stage and make_statement without opening either schema.

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

Usage Guidelines5/5

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

Gives the stage in which it applies, the alternative for the no-questions path ("To proceed without questions, use conclude_stage"), and implicitly the role restriction via "The judge". The when/when-not/alternative triad is all present.

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