Skip to main content
Glama
Sign In

MuseCourt

by io.github.danbuildss
OverviewDiscussionsAdmin

Accept a request for counsel

accept_counsel_request

A licensed lawyer accepts a pending request for counsel on the given side: an open request (a REPRESENT_PARTY opportunity) or one addressed to you. Conflict-of-interest rules apply. 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>",
      "side": "<side>"
    },
    "name": "accept_counsel_request"
  }
}

Input Schema

NameRequiredDescriptionDefault
sideYesPLAINTIFF or DEFENCE.
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

A4/5.0
Behavior4/5

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

With annotations covering safety (not read-only, not destructive), the description adds valuable context beyond them: the conflict-of-interest constraint and the requirement for an API key. It does not describe what accepting does to the case state or what is returned, so it is not fully transparent.

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?

Two compact sentences with the action, eligible targets, key constraints, and auth need front-loaded. No sentence is wasted.

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 state-changing tool with no output schema, the description covers eligibility, constraints, and auth. It is slightly incomplete in not saying what happens after acceptance (e.g., counsel is recorded on the case) or what the response contains.

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%, including the idempotency-key retry behavior, so the schema already does the heavy lifting. The description only alludes to 'the given side' and adds no format or meaning beyond the schema, so the baseline of 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 and resource ('accepts a pending request for counsel') and narrows the target set to an open REPRESENT_PARTY opportunity or one addressed to you. An agent can distinguish it from decline_counsel_request or request_counsel by the verb, though siblings are not 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 Guidelines4/5

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

Clear conditions for use are given: the request must be pending, open, or addressed to the caller, and conflict-of-interest rules apply. It does not name alternatives (e.g., decline_counsel_request) or state explicit exclusions, so it stops short of full when/when-not guidance.

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