Skip to main content
Glama

insc.one — INSC.1 Citation Layer

get_ratio

Return the extractive, paragraph-anchored ratio decidendi and headnotes of a Supreme Court case. Never paraphrased; every holding carries a paragraph anchor.

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

Input Schema

NameRequiredDescriptionDefault
issueNoOptional focus issue or statutory section.
citationYesINSC neutral citation or any resolvable reference.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / issue / description
      Previous value: -"Optional focus issue or statutory section to prioritize relevant headnotes."New value: +"Optional focus issue or statutory section."
  2. Changed1 schema field changed
    • changedInput schema / properties / issue / description
      Previous value: -"Optional focus issue or statutory section."New value: +"Optional focus issue or statutory section to prioritize relevant headnotes."
  3. Changed1 schema field changed
    • changedInput schema / properties / issue / description
      Previous value: -"Optional focus issue or statutory section to prioritize relevant headnotes."New value: +"Optional focus issue or statutory section."
  4. First observed

TDQS

A3.8/5.0
Behavior4/5

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

No annotations are supplied, so the description carries the burden, and it does disclose a substantive behavioral property beyond the schema: output is extractive and 'never paraphrased', with every holding paragraph-anchored, which tells the agent the results are verifiable against source text and safe to cite. It still omits failure behavior (unresolvable citation, case without headnotes), size/length of the returned holdings, and any permission or rate-limit context.

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, zero padding, and the core guarantee ('Never paraphrased') is front-loaded in the second sentence where it reads as an invariant. Nothing could be removed without losing meaning.

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 only two parameters, no nesting, and no output schema, the description covers the essential contract: what is returned conceptually (ratio decidendi plus headnotes) and its fidelity guarantee. A brief note on return structure or behavior when no ratio is found would close the remaining gap.

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%, so both parameters are already documented in the input schema. The description adds nothing about how 'issue' narrows the returned ratio or what forms of reference 'citation' resolves, so the 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 verb ('Return') and a precisely characterized resource ('extractive, paragraph-anchored ratio decidendi and headnotes of a Supreme Court case'). An agent knows exactly what it gets. It does not name a sibling or contrast itself with search_cases or check_treatment, so sibling differentiation is absent.

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 only implied by the scope phrase 'of a Supreme Court case' — the agent must infer that this is for pulling the holding once a case is identified. There is no explicit 'use this when' statement, no exclusions, and no pointer to resolve_citation or search_cases as prerequisites for obtaining the citation.

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