Skip to main content
Glama

refresh_bill_index

Read-only

Updates the local bill search index for a session, processing only changed bills by default or all bills with full=True, and reports background build progress.

Instructions

Update the local search index for a session (only changed bills unless full=True), or check on a background build's progress.

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": "refresh_bill_index"
  }
}

Input Schema

NameRequiredDescriptionDefault
fullNoRefetch every bill (slow; runs in the background).
sessionNoSession, e.g. '2026', '2026GS', '2025S1'. Omit for the current general session.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior4/5

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

Beyond the annotations, the description discloses three real behavioral traits: the default is incremental ('only changed bills'), the full path is expensive and runs in the background, and the same tool doubles as a progress check. There is a mild tension between 'Update' and readOnlyHint=true, though building a derived local index is defensibly a read-only operation against the external source.

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?

A single sentence with two well-ordered clauses; the primary update behavior and its default come first, the polling mode second. No filler, though the line break and parenthetical make it read slightly denser than needed.

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?

There is no output schema, so the description carries the burden of describing what comes back — and it does not say what a progress check returns (percentage, status string, bill counts) or whether the call blocks. For a two-parameter tool with full schema coverage this is adequate but leaves a real gap around return values.

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 schema already defines both parameters; the baseline would be 3. The description earns above that by naming the default behavior ('only changed bills') that the schema does not state, making the contrast with full=True explicit rather than leaving it to be inferred from the property description.

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 states a specific verb and resource ('Update the local search index for a session') and adds a second mode ('check on a background build's progress'). No sibling tool deals with indexing, so the operation is unambiguous, though the dual update/poll purpose in one sentence is slightly blurry.

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 implies usage contexts — call it to refresh the index, or to poll a build that is running in the background — and the 'unless full=True' clause implies a cheap default path. But there is no explicit when-not guidance, no prerequisite stated (e.g., whether the session must exist or be loaded first), and no named alternative.

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