Skip to main content
Glama

get_fiscal_note

Read-only

Retrieve a bill's fiscal note as paged plain text to review estimated revenue and expenditure impacts.

Instructions

Read a bill's fiscal note (estimated revenue/expenditure impact) as plain text, paged.

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>"
    },
    "name": "get_fiscal_note"
  }
}

Input Schema

NameRequiredDescriptionDefault
billYesBill number, e.g. 'HB 1', 'SB42', 'HJR 3'.
offsetNoStart position for paging; use next_offset from a prior call.
sessionNoSession, e.g. '2026', '2026GS', '2025S1'. Omit for the current general session.
max_charsNoCharacter budget for this response (500-20000). Defaults to the server setting.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds two useful behavioral facts beyond that — output is plain text rather than structured, and responses are paged — but it omits the practically important case of a bill with no fiscal note (empty result vs. error).

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?

A single front-loaded sentence: what is read, what it means, how it is returned, and that it is paged. No filler and nothing buried.

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 simple four-parameter read tool with full schema coverage and no output schema, the definition states resource, format, and paging adequately. The main residual gap is the absent-fiscal-note case, which matters for an open-world fetch.

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%, and the four parameters (bill, offset, session, max_chars) each carry their own explanation including paging and the current-session default. The description only echoes 'paged' and adds no format or semantics beyond the schema, so 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?

Names a specific verb and resource (read a bill's fiscal note) and disambiguates the domain term with a parenthetical defining it as estimated revenue/expenditure impact, plus states the output form (plain text). It stops short of contrasting with the closest sibling, read_bill_text, leaving the agent to infer that fiscal notes are not bill text.

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: the agent can infer this is the tool for fiscal-impact material rather than bill text or history. There is no explicit when-to-use, no when-not-to-use, and no statement of what to do when a bill has no fiscal note.

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