Skip to main content
Glama

Id Search

id_search
Read-onlyIdempotent

Search the Idaho Statutes BY TOPIC or keyword rather than citation, "landlord security deposit", "concealed weapon permit", "child custody". Matches against the Idaho Legislature's own official chapter and section CATCHLINES across all ~20,400 sections (not full statutory prose, Idaho does not publish a keyless full-text search API, verified live; its hosted search box has no documented contract). Returns matching citations and catchlines; call id_statute with a citation for the full text. Keyless.

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

Input Schema

NameRequiredDescriptionDefault
limitNoMax results to return, default 10, max 25.
queryYesTopic or keywords, e.g. "landlord security deposit".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive and openWorld, so the safety profile is covered. The description does add meaningful behavior the annotations cannot: matching is against official catchlines only over ~20,400 sections, not full statutory prose, and the service is keyless. However it stops short of describing result ordering or empty-result behavior.

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?

The key scoping constraint is front-loaded in the first clause, followed by examples and the return/next-step contract. The parenthetical justifying why full-text search is unavailable ("verified live; its hosted search box has no documented contract") is slightly self-indulgent but still supports the catchline-only caveat.

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 two-parameter search tool with no output schema, the description covers the matching source, approximate corpus size, return shape (citations and catchlines), and the follow-up call needed for full text. Nothing an agent needs to invoke 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 real semantic meaning by explaining WHAT the query is matched against (chapter/section catchlines, not prose), which shapes how an agent should phrase queries. The limit parameter is left entirely to the schema, keeping it from a 5.

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 ("Search the Idaho Statutes") plus the scope qualifier "BY TOPIC or keyword rather than citation," which separates it cleanly from the citation-lookup sibling id_statute. Example topical queries make the intent concrete.

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?

Clear when-to-use (topic/keyword lookups, with three sample phrasings) and an explicit handoff — "call id_statute with a citation for the full text." It does not spell out an explicit when-not-to-use case beyond "rather than citation," so it falls just short of the top mark.

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.