Skip to main content
Glama

BRAINIAC Bills & eCFR Section Lookup

Look up UK Parliament bill status

legislative-intelligence_uk-parliament-bill-status
Read-onlyIdempotent

Return the current stage and outcome of a UK Parliament bill from the vendored Bills API export. Price $0.03 USDC. POST /api/v1/legislative-intelligence/uk-parliament-bill-status. An unpaid call returns the x402 payment terms and does not run.

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": "legislative-intelligence_uk-parliament-bill-status"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNolimit, integer. Optional.
queryNoquery, string. Optional.
billIdNobillId, integer. Optional.
sessionIdNosessionId, integer. Optional.

Output Schema

NameRequiredDescriptionDefault
foundNofound. Boolean.
resultsNoresults. Array.
sourcesNosources. Array.
exportedAtNoexportedAt. String.
limitationsNolimitations. Array.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and openWorld, so the safety profile is covered. The description adds value beyond them by disclosing the price ($0.03 USDC), the endpoint, and the payment-gate failure behavior, which an agent must know before calling.

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?

Three short sentences, front-loaded with the purpose followed by cost and payment behavior. Every sentence carries operational value; only the raw endpoint string is arguably redundant detail.

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?

An output schema exists, so return-value explanation is unnecessary, and annotations carry the safety profile. What remains is the payment prerequisite and endpoint, both supplied; only interaction between the optional filter parameters is left unexplained.

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 all four parameters (limit, query, billId, sessionId) are already documented structurally. The description adds no meaning about lookup precedence or optionality, which matches the baseline for fully documented schemas.

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 verb and resource ('Return the current stage and outcome of a UK Parliament bill') and scopes the data source ('vendored Bills API export'), which implicitly separates it from the congress-bill-status sibling by jurisdiction. It stops short of naming an alternative explicitly, but an agent can identify the tool's job.

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 context is implied rather than stated: it covers retrieving UK bill status and mentions that an unpaid call returns payment terms instead of running, which is a real prerequisite. There is no explicit when-to-use/when-not-to-use guidance or reference to the sibling tools.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources