Skip to main content
Glama

find_in_bill

Read-only

Search a bill’s text by term or regex and return matching snippets with section IDs to locate relevant passages; loads the bill automatically when needed.

Instructions

Search inside a bill's text and return only matching snippets with their section ids (loads the bill if needed). Use read_bill_text(section=..., offset=...) to read around a hit.

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": {
      "bill": "<bill>",
      "pattern": "<pattern>"
    },
    "name": "find_in_bill"
  }
}

Input Schema

NameRequiredDescriptionDefault
billYesBill number, e.g. 'HB 1', 'SB42', 'HJR 3'.
regexNoTreat pattern as a regular expression.
patternYesText to find (case-insensitive).
sessionNoSession, e.g. '2026', '2026GS', '2025S1'. Omit for the current general session.
max_hitsNo
max_charsNoCharacter budget for this response (500-20000). Defaults to the server setting.
context_charsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior4/5

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

Annotations only declare readOnlyHint and openWorldHint; the description adds the non-obvious side effect that the bill is loaded into the session if not already present, which matters for later calls. It also discloses that only snippets plus section ids come back rather than full text. It stops short of saying what happens when hits exceed the limit or how the character budget truncates results.

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, purpose and scope front-loaded, followed immediately by the actionable next step. Nothing is repeated from the schema and no sentence is filler.

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 seven-parameter search tool with no output schema, the description covers purpose, return shape, implicit loading behavior, and the follow-up path, while the schema carries the parameter details. The remaining gap — truncation and hit-limit behavior — is modest but would help an agent interpret partial results.

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 coverage is 71%, so most parameters (bill, pattern, regex, session, max_chars) are already documented in the schema and the description adds nothing about them. Its one contribution is tying the returned section ids to read_bill_text's section parameter, which is meaningful but narrow. A 3 baseline is appropriate here.

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?

"Search inside a bill's text and return only matching snippets with their section ids" gives a precise verb, an explicit scope restriction (inside one bill's text, not across bills), and the shape of the return value. An agent can distinguish it from search_bills and from read_bill_text without opening the schema.

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?

It routes the agent forward — "Use read_bill_text(section=..., offset=...) to read around a hit" — which is genuinely useful workflow guidance. It gives no when-not guidance, e.g. no statement about what to use for searching across many bills or for locating a bill by keyword in its title.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.