Skip to main content
Glama

insc.one — INSC.1 Citation Layer

check_treatment

Check whether a cited Supreme Court authority is still good law — overruled, distinguished, or affected by a larger bench under the Article 141 hierarchy. Run before including any authority.

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": {
      "citation": "<citation>"
    },
    "name": "check_treatment"
  }
}

Input Schema

NameRequiredDescriptionDefault
citationYesINSC neutral citation or any resolvable reference.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/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 disclosure burden. It does useful domain work by naming the treatment classes it detects, but it omits what the response looks like (status field, reasoning, confidence), how an unresolvable or non-existent citation is handled, and whether the check is against a static database or live source.

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, front-loaded with the core check and closed with the imperative call-to-action. No filler, no restatement of the tool name.

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 single-parameter, annotation-free tool with no output schema, the description supplies enough to call it correctly and understand its domain. The one material gap is return-value shape, which the enumeration of treatment classes only partially covers.

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?

One parameter with 100% schema coverage; the schema already explains that a neutral citation or any resolvable reference is accepted. The description adds no format examples, normalization rules, or failure conditions beyond that, so the schema does all the work — baseline 3.

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?

Specific verb and resource: checks whether a cited Supreme Court authority is still good law, enumerating the outcomes it detects (overruled, distinguished, affected by a larger bench). The scope ('Article 141 hierarchy') is narrow enough that an agent won't confuse it with format_citation or resolve_citation, though it never explicitly contrasts itself with those siblings.

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

Usage Guidelines4/5

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

'Run before including any authority' gives a clear, actionable trigger condition tied to a workflow step. It stops short of naming alternatives or stating when NOT to use it (e.g. for non-Supreme Court or unresolved citations), so the guidance is directional rather than complete.

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