Skip to main content
Glama
Federal Courts Analyst

Federal Courts Analyst

Open a request (sandbox)

open_request
Idempotent

Create a request on the sandbox request desk to ask the statistics office why a figure changed, save a verified copy, or receive alerts when its numbers change; user confirmation required.

Instructions

Use this only when the user explicitly asks to keep an answer: to ask the statistics office why a figure changed (option 'ask_office'), to save a verified copy ('verified_copy'), or to be notified if its numbers change ('notify'). It creates a request on the sandbox request desk. Answering a question never needs it; never call it on your own initiative.

Not for answering questions (use get_official_figure, explain_change and the other read tools) or for saving the answer text (call save_verified_answer next, with the answer and its citations).

Returns the new request: its number, status and inbox updates. It writes only after the user confirms; without confirmation it returns a preview. Sandbox: nothing is sent to the AO or the FJC.

Example: option='ask_office', question='Why did FY2020 national weighted civil filings per judgeship change from 554 to 322?' → request #1001, status 'received'.

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": {
      "option": "<option>",
      "question": "<question>"
    },
    "name": "open_request"
  }
}

Input Schema

NameRequiredDescriptionDefault
optionYesWhat the user wants kept.
confirmNoTrue once the user has agreed to this write. False (default) asks the user, or returns a preview if the client can't ask.
questionYesThe user's question.
asker_nameNoA display name for the asker (demo identity; the same name must be used for every call about one request).MCP user
asker_roleNoWho is asking.public
idempotency_keyNoAny unique string; a retried call with the same key returns the first result instead of writing again.

Output Schema

NameRequiredDescriptionDefault
dataNo
statusNook
declinedNo
warningsNo
provenanceNo
clarificationNo
suggested_nextNoHints for a follow-up call.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.8/5.0
Behavior5/5

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

Annotations declare readOnlyHint=false and idempotentHint=true, but the description adds the crucial non-structured behavior: the write happens only after user confirmation, otherwise a preview is returned. It also discloses the sandbox scope ('nothing is sent to the AO or the FJC') and the return contents (request number, status, inbox updates).

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?

Front-loads the usage constraint, then behavior, then alternatives, then an illustrative example — a sensible order with little waste. The example is somewhat long but earns its place by demonstrating the required 'question' parameter and expected return.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Covers confirmation semantics, sandbox scope, and side effects; return values are also backed by an output schema. Nothing an agent needs in order to call this write tool safely is missing.

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 baseline is 3, but the description adds real meaning by explaining what each enum value of 'option' means semantically ('why a figure changed', 'save a verified copy', 'be notified if its numbers change'), which the schema only labels as 'What the user wants kept.'

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 the specific verb and resource ('creates a request on the sandbox request desk') and enumerates the three concrete request kinds (ask_office, verified_copy, notify). An agent can distinguish it from read siblings at a glance.

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?

Explicit gating: 'Use this only when the user explicitly asks to keep an answer' and 'never call it on your own initiative.' It names the read alternatives (get_official_figure, explain_change) and the follow-up write (save_verified_answer), so both the when and the when-not are covered.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.