CaseMagic — Federal Court Case Lookup & Monitor

Save a case to the account

create_case_passport

Idempotent

Save a case that find_federal_case just located to the signed-in CaseMagic account, which creates its Case Passport — the persistent record of the matter — and its permanent CaseMail address. Use this after the user has confirmed which case is theirs and wants CaseMagic to keep it. Requires the connect_token from that lookup, which expires shortly afterwards.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`user_role`	Yes	The user's own role in the case. Ask them rather than guessing.
`connect_token`	Yes	The connect_token returned by find_federal_case for the case the user confirmed.

Output Schema

TableJSON Schema

Name	Required	Description
`case`	No	Caption, number and court of the saved case.
`error`	No	Present only when the call failed: a code, a message and, where there is one, an action such as a link to give the user.
`docket`	No	Docket size and latest activity.
`passport_id`	No	Case Passport id.
`passport_version`	No	Passport version.
`organization_matter_id`	No	The saved case’s matter id.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 5, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "properties": {
+    "case": {
+      "additionalProperties": true,
+      "description": "Caption, number and court of the saved case.",
+      "properties": {},
+      "type": "object"
+    },
+    "docket": {
+      "additionalProperties": true,
+      "description": "Docket size and latest activity.",
+      "properties": {},
+      "type": "object"
+    },
+    "error": {
+      "additionalProperties": true,
+      "description": "Present only when the call failed: a code, a message and, where there is one, an action such as a link to give the user.",
+      "properties": {
+        "code": {
+          "description": "Machine-readable error code, for example CASE_NOT_FOUND or MULTIPLE_CASES_FOUND.",
+          "type": "string"
+        },
+        "message": {
+          "description": "What went wrong, in a sentence.",
+          "type": "string"
+        }
+      },
+      "type": "object"
+    },
+    "organization_matter_id": {
+      "description": "The saved case’s matter id.",
+      "type": "string"
+    },
+    "passport_id": {
+      "description": "Case Passport id.",
+      "type": "string"
+    },
+    "passport_version": {
+      "description": "Passport version.",
+      "type": "number"
+    }
+  },
+  "type": "object"
+}

First observedSep 24, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint=false, destructiveHint=false, idempotentHint=true), so the description doesn't need to restate them. It adds real value beyond them: the tool creates a persistent record and a permanent CaseMail address, and the connect_token has a short expiry — both operationally important. It doesn't say what happens if the token has expired or how duplicate saves are handled.

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 sentences, no filler: what it does and what it creates first, then when to use it, then the prerequisite. Front-loaded and every sentence earns its place.

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?

With an output schema present, return values need not be explained. The description covers purpose, side effects, the prerequisite token and its expiry, and the confirmation gate — everything an agent needs to invoke it correctly given the two-parameter schema.

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 coverage is 100%, including an enum on user_role with its own 'ask them rather than guessing' guidance, so the schema does the heavy lifting (baseline 3). The description adds only the token's provenance and expiry hint, which is genuine but marginal.

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 verb and resource ('Save a case... to the signed-in CaseMagic account') and immediately clarifies the side effects (creates Case Passport and permanent CaseMail address). It explicitly ties back to find_federal_case, distinguishing it from get_case_passport and list_my_cases.

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 an explicit trigger ('Use this after the user has confirmed which case is theirs and wants CaseMagic to keep it'), names the prerequisite tool that produces the required token, and warns the token expires shortly. An agent knows exactly when to call it and with what.

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

All CaseMagic — Federal Court Case Lookup & Monitor 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.

Resources

Need Help?