Skip to main content
Glama

list_bill_requests

Read-only

Retrieve unnumbered bill requests for a session, including titles and sponsor IDs, to find drafts being prepared. Filter by title or sponsor and page results as needed.

Instructions

Unnumbered bill requests (drafts being prepared) for a session, with titles and sponsor ids.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_bill_requests"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax items to return (1-50).
queryNoOnly requests whose title contains this text.
offsetNoStart position for paging; use next_offset from a prior call.
sessionNoSession, e.g. '2026', '2026GS', '2025S1'. Omit for the current general session.
sponsorNoOnly requests whose sponsor id contains this.
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

B3.3/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 safety is covered. The description adds worthwhile domain context that these are unnumbered drafts in preparation, but says nothing about ordering, pagination behavior, or result volume limits beyond what the schema already states.

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 that identifies the resource, its distinguishing nature, its scope, and its return contents with no wasted words.

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

Completeness3/5

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

With no output schema, the description does well to name the returned fields, and the schema itself handles paging and filtering. However, for a six-parameter listing tool it omits result ordering, whether drafts include text or status, and how this relates to sibling listing tools.

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 100%, so every parameter is already documented, including session format examples and paging semantics. The description only echoes session scoping and sponsor ids, adding little beyond the schema, which is the expected baseline.

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?

The description gives a specific resource ('unnumbered bill requests') and clarifies it means drafts being prepared, scoped to a session, and states the returned fields (titles, sponsor ids). It does not explicitly contrast with siblings like list_bills or search_bills, so the agent must infer the difference between unnumbered drafts and numbered bills.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use or when-not-to-use guidance, and no alternative is named. An agent must infer that this tool is for pre-filing drafts while list_bills covers numbered bills; that inference is left entirely unassisted.

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