Skip to main content
Glama

unload_bill

Read-only

Removes a bill from working memory to free context, optionally scoped to a session. Use it when a bill no longer needs to remain loaded.

Instructions

Remove a bill from working memory.

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

Input Schema

NameRequiredDescriptionDefault
billYesBill number, e.g. 'HB 1', 'SB42', 'HJR 3'.
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.5/5.0
Behavior3/5

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

The annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds the important behavioral scoping that the effect is limited to working memory rather than persisted bill data, but it does not say whether removal is idempotent, whether it raises an error for an unloaded bill, or how it interacts with the session parameter.

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 short sentence, front-loaded with the action and its scope, with no redundant restatement of the name or title. Nothing in it is filler.

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?

For a two-parameter state-management tool with no output schema, the definition covers the core effect but omits the consequences an agent needs: what subsequent calls against the unloaded bill will do, and whether removal affects other loaded bills. It is adequate but noticeably thin.

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%, so both the bill identifier format and the session defaulting rule are already documented in the schema. The description contributes nothing about parameters, which is acceptable at full coverage but leaves the baseline unimproved.

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 names a specific verb and resource ("Remove a bill") and adds scope ("from working memory"), which distinguishes this session-state operation from data-fetching siblings like get_bill. It stops short of naming its natural counterpart, load_bill, so the pairing must be inferred from the name.

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 implied rather than stated: an agent can reason that this undoes load_bill and relates to list_loaded_bills, but the definition never says when to call it, whether it is needed before switching sessions, or what happens if the bill was never loaded.

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