Skip to main content
Glama

insc.one — INSC.1 Citation Layer

resolve_citation

Resolve any Indian Supreme Court reference — INSC neutral citation, SCC, AIR, MANU, party name + year, or free text — to the canonical INSC neutral citation with parallel citations, bench, decision date, official e-SCR link, and current treatment status.

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": "resolve_citation"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYesThe reference to resolve, e.g. "2013 INSC 768", "(2014) 2 SCC 1", "Lalita Kumari".

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / query / description
      Previous value: -"The reference to resolve, e.g. \"2013 INSC 768\", \"(2014) 2 SCC 1\", \"AIR 2014 SC 187\", \"Lalita Kumari\", \"Arnesh Kumar arrest\"."New value: +"The reference to resolve, e.g. \"2013 INSC 768\", \"(2014) 2 SCC 1\", \"Lalita Kumari\"."
  2. Changed1 schema field changed
    • changedInput schema / properties / query / description
      Previous value: -"The reference to resolve, e.g. \"2013 INSC 768\", \"(2014) 2 SCC 1\", \"Lalita Kumari\"."New value: +"The reference to resolve, e.g. \"2013 INSC 768\", \"(2014) 2 SCC 1\", \"AIR 2014 SC 187\", \"Lalita Kumari\", \"Arnesh Kumar arrest\"."
  3. Changed1 schema field changed
    • changedInput schema / properties / query / description
      Previous value: -"The reference to resolve, e.g. \"2013 INSC 768\", \"(2014) 2 SCC 1\", \"AIR 2014 SC 187\", \"Lalita Kumari\", \"Arnesh Kumar arrest\"."New value: +"The reference to resolve, e.g. \"2013 INSC 768\", \"(2014) 2 SCC 1\", \"Lalita Kumari\"."
  4. First observed

TDQS

A4/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 burden. It does disclose the return payload (parallel citations, bench, decision date, e-SCR link, treatment status), which is real value, but says nothing about ambiguity handling, what happens with an unresolvable or non-Supreme-Court reference, error behavior, or any auth/rate constraints.

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?

A single front-loaded sentence: verb, accepted input space, then output payload. No filler, no restatement of the title, and the most decision-relevant information (what forms it accepts) comes first.

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 one-parameter lookup with no output schema, enumerating the returned fields is exactly what is needed, and the accepted-format list removes the main ambiguity about what to pass. The gap is failure/ambiguity semantics and the boundary against check_treatment for the treatment-status field.

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% and there is a single optional-free required parameter, so baseline is 3; the description goes beyond the schema's three illustrative examples by naming the full accepted grammar (neutral cite, SCC, AIR, MANU, party+year, free text). That materially widens what an agent knows it can pass in.

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?

Names a specific verb ('Resolve') and resource ('Indian Supreme Court reference'), enumerates exactly which reference formats it accepts (INSC, SCC, AIR, MANU, party name + year, free text), and states the canonical output. An agent can tell this is a normalization/lookup operation, distinct from formatting, searching, or treatment-checking siblings.

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?

Usage is implied by the input-format enumeration: call it when you hold any citation form and need the canonical INSC cite. There is no explicit when-not clause and no routing against siblings such as format_citation or check_treatment — notable since this tool also returns 'current treatment status', which overlaps conceptually with check_treatment and is left unaddressed.

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