Skip to main content
Glama

Id Statute

id_statute
Read-onlyIdempotent

Get the FULL TEXT of a section of the Idaho Statutes (Idaho Code) by citation. "18-4001" is murder; "32-717" lists child custody factors. Accepts natural forms: "18-4001", "Idaho Code 18-4001", "I.C. section 18-4001". Returns the current statutory text, the official catchline, chapter/title context, and the amendment HISTORY line Idaho prints on nearly every section (e.g. "[18-4001, added 1972, ch. 336, sec. 1, p. 928; am. 1977...]"). Idaho publishes the CURRENT text only, no per-year historical archive of statute text (only session-law PDF volumes organized by session chapter, not by Code citation); this tool says so rather than guessing. Keyless. Use for "what does Idaho Code 18-4001 say" or to check an Idaho statute a case or lease relies on.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "citation": "18-4001"
    },
    "name": "id_statute"
  }
}

Input Schema

NameRequiredDescriptionDefault
citationYesSection citation, title-number, e.g. "18-4001" (murder) or "55-307" (landlord access to leased premises). Some sections carry a letter suffix, e.g. "18-101A".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive/openWorld, and the description still adds substantial context: what is returned (statutory text, official catchline, chapter/title context, amendment HISTORY line), that authentication is not required ('Keyless'), and an explicit limitation that no per-year historical archive exists and the tool will say so instead of guessing. That limitation disclosure is exactly the kind of behavior annotations cannot convey.

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?

Front-loaded with the verb, resource, and example citations, and each subsequent clause carries real information (return contents, citation formats, archive limitation, keyless access). The parenthetical digression about session-law PDF volumes is the longest and least actionable stretch, keeping it from a 5.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a single-parameter, no-output-schema tool, the description covers everything an agent needs: what it fetches, accepted input formats, what comes back, the coverage limitation, and that no key is required. Nothing needed to call it correctly is missing.

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%, so the baseline is 3, but the description adds genuinely new meaning by listing accepted natural citation forms ("Idaho Code 18-4001", "I.C. section 18-4001") that the schema's bare '18-4001' example does not imply. The letter-suffix note ("18-101A") duplicates the schema, but the format tolerance is an added value.

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?

States a specific verb and resource: 'Get the FULL TEXT of a section of the Idaho Statutes (Idaho Code) by citation,' and immediately grounds it with two concrete citations ("18-4001" murder, "32-717" child custody factors). This clearly separates it from a search-style sibling, since the input is a known citation rather than a query.

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?

Gives explicit usage triggers: answering 'what does Idaho Code 18-4001 say' or verifying a statute that a case or lease relies on, plus a clear when-not ('Idaho publishes the CURRENT text only, no per-year historical archive'). It stops short of naming id_search as the alternative when the agent lacks a citation, so routing for lookup-by-topic 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.