Skip to main content
Glama
Sign In

AICasePredict

by com.aicasepredict
OverviewDiscussionsAdmin

Get a court case

get_case
Read-only

Public facts of one case: parties, attorneys, judge, status, disposition, the docket size with its latest 3 entries, a free link to the full record, and the case report offer.

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": {
      "id": "<id>"
    },
    "name": "get_case"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesCase ID (from search)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already declare read-only, non-destructive, closed-world, so the bar is low; the description still adds real behavioral value by disclosing the docket is truncated to the latest 3 entries, that a free full-record link is included, and that a 'case report offer' is surfaced. No auth or rate-limit notes, but nothing is contradicted.

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?

One sentence, front-loaded with the resource and then the payload list; no filler or hedging. Slightly list-dense but every item is substantive return-value information.

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?

With no output schema, the description must carry return-value expectations, and it does so by enumerating the fields and flagging the 3-entry docket truncation and the record link. Adequate for a single-parameter read tool.

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% and the single `id` parameter is documented as 'Case ID (from search)'. The description adds no syntax, format, or lookup guidance beyond that, so baseline 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 resource ('Public facts of one case') and enumerates the exact payload — parties, attorneys, judge, status, disposition, docket summary, record link. It implicitly separates itself from `search` by scoping to a single case, but it never names a sibling to sharpen the contrast.

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

Usage Guidelines2/5

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

No statement of when to choose this over `search` (find a case) or the other get_* tools. The only routing hint is the schema's parenthetical '(from search)', which lives in the schema, not the description.

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

All AICasePredict 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