Skip to main content
Glama

insc.one — INSC.1 Citation Layer

search_cases

Search the insc.one Supreme Court index by natural-language issue, keyword, or legal proposition. Returns ranked cases with INSC citations, one-line holdings, and treatment signals.

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": {
      "query": "<query>"
    },
    "name": "search_cases"
  }
}

Input Schema

NameRequiredDescriptionDefault
yearNoOptional 4-digit year to restrict S3-index results (1950–2026).
limitNo
queryYesNatural-language legal question or keywords.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / query / description
      Previous value: -"Natural-language legal question or keywords, e.g. 'FIR mandatory registration', 'anticipatory bail charge sheet', 'CoC commercial wisdom IBC'."New value: +"Natural-language legal question or keywords."
  2. Changed1 schema field changed
    • changedInput schema / properties / query / description
      Previous value: -"Natural-language legal question or keywords."New value: +"Natural-language legal question or keywords, e.g. 'FIR mandatory registration', 'anticipatory bail charge sheet', 'CoC commercial wisdom IBC'."
  3. Changed1 schema field changed
    • changedInput schema / properties / query / description
      Previous value: -"Natural-language legal question or keywords, e.g. 'FIR mandatory registration', 'anticipatory bail charge sheet', 'CoC commercial wisdom IBC'."New value: +"Natural-language legal question or keywords."
  4. Changed2 schema fields changed
    • changedInput schema / properties / query / description
      Previous value: -"Natural-language legal question or keywords, e.g. 'FIR mandatory registration', 'CoC commercial wisdom IBC'."New value: +"Natural-language legal question or keywords, e.g. 'FIR mandatory registration', 'anticipatory bail charge sheet', 'CoC commercial wisdom IBC'."
    • addedInput schema / properties / year
      Added value: +{
      +  "description": "Optional 4-digit year to restrict S3-index results (1950–2026).",
      +  "type": "string"
      +}
  5. First observed

TDQS

A3.6/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full behavioral burden. It does disclose the return payload (ranked cases, INSC citations, one-line holdings, treatment signals), which is useful, but it says nothing about corpus coverage, ranking logic, latency, result limits, or whether the treatment signals are authoritative or preliminary.

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 sentences with zero filler; the search scope comes first and the return contract second. Every clause adds information an agent needs.

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 three-parameter read-only search tool with no output schema, the description covers the essentials: what can be queried and what comes back. The gaps (limit behavior, empty-result handling, whether year narrows to an S3 subset) are real but modest.

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 67%, and the description only echoes the query parameter's meaning while adding the 'legal proposition' phrasing. The year restriction (1950-2026, S3-index scoping) and the limit cap of 15 are documented only in the schema, not reinforced or explained in the description.

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 (search) plus resource (the insc.one Supreme Court index) and enumerates the query modes: natural-language issue, keyword, or legal proposition. It also previews the return shape. It never names a sibling such as check_treatment or check_cross_citations, so the agent must infer this is the discovery entry point rather than a look-up tool.

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?

Implicit guidance is present: it is a search tool for open-ended issues, which contrasts with the targeted check_*/get_* siblings. But there is no explicit when-to-use or when-not statement, and no instruction on when to follow up with check_treatment or get_ratio, so the routing is left to inference.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources