Skip to main content
Glama
Sign In

MuseCourt

by io.github.danbuildss
OverviewDiscussionsAdmin

Offer a settlement

offer_settlement

A party (or its counsel) offers terms to the other side at any open stage. If accepted, the case closes as settled, 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>",
      "terms": "<terms>"
    },
    "name": "offer_settlement"
  }
}

Input Schema

NameRequiredDescriptionDefault
termsYesThe terms (up to 2000 characters).
caseIdYesThe case number (OC-0001) or case ID (case_…).
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?

Annotations already declare the mutation profile (readOnlyHint=false, destructiveHint=false), and the description adds real consequence the annotations cannot convey: acceptance closes the case as settled with no verdict. It also flags the API-key requirement. It does not explain what happens on rejection or whether terms are revocable, but the key behavioral outcome is 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 action front-loaded and no filler; the outcome and auth note each carry weight. The trailing "Needs your API key" is terse to the point of feeling appended rather than integrated.

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 no-output-schema mutation tool it covers the action, timing, and terminal consequence, which is the essential set. It leaves open the post-rejection path and whether a party may re-offer, gaps a settlement workflow tool should probably address.

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 caseId, terms, and idempotencyKey are each documented in the schema and the baseline of 3 applies. The description adds no syntax, format, or constraint detail beyond what the schema already provides.

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 ("offers terms to the other side") plus the actor (party or counsel), which clearly separates it from read siblings like get_case. It does not explicitly distinguish itself from the closely-related respond_to_settlement and withdraw_settlement_offer, so the agent must infer the boundary.

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?

"At any open stage" gives a usable trigger condition, and the acceptance outcome clarifies intent. However, it never says when NOT to use it (e.g. no open case), nor does it route the agent to respond_to_settlement for replying to a received offer or to withdraw_settlement_offer to retract one.

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