Skip to main content
Glama
paulieb89

UK Legal Research MCP Server

Get Bill Detail

bills_get_bill
Read-onlyIdempotent

Given a bill ID, retrieves full bill details: sponsors, current stage, long title, summary, and Royal Assent date. Summary length is adjustable via max_summary_chars parameter.

Instructions

USE THIS TOOL WHEN you have a bill_id (from bills_search_bills) and want the full detail.

Returns sponsors, current stage, long title, summary, and Royal Assent date if enacted. Summary text is capped per max_summary_chars — check summary_truncated in the response.

AFTER calling, use parliament_search_hansard(query=bill_short_title) to find the bill's parliamentary debates, or bills_search_bills with a related keyword for adjacent bills.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
bill_idYesBill ID from bills_search_bills results.
max_summary_charsNoMaximum characters of the bill summary text to return. Default 5,000 (~1,250 tokens) covers most bills. Raise for substantive government bills (Finance Act, Levelling-up) whose summary runs longer. Check summary_truncated in the response to see if it was cut.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesBill ID
short_titleYesShort title of the bill
long_titleNoFull long title
summaryNoBill summary text, possibly truncated per max_summary_chars. Check summary_truncated and summary_original_length for full-text info.
summary_truncatedNoTrue if summary was cut to fit max_summary_chars
summary_original_lengthNoOriginal summary length in characters before any truncation
current_houseNoHouse where the bill currently sits
originating_houseNoHouse where the bill was introduced
current_stageNoCurrent legislative stage
sponsorsNoBill sponsors
stagesNoLegislative stages the bill has passed through
is_actNoWhether the bill has received Royal Assent
royal_assent_dateNoDate Royal Assent was given
urlYesParliament URL for this bill
Behavior4/5

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

Annotations already indicate readOnlyHint, idempotentHint, and destructiveHint false. The description adds behavioral details beyond annotations: the summary truncation behavior (capped per max_summary_chars with a truncation flag) and conditional inclusion of Royal Assent date. No contradictions.

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?

The description is concise with three sentences, each serving a distinct purpose: usage condition, return fields with caveat, and follow-up actions. No superfluous information.

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

Completeness5/5

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

Given the tool has only 2 parameters and an output schema, the description covers all necessary aspects: purpose, exact usage condition, parameter behavior, return fields, and recommended follow-up steps. It is complete for an agent to correctly invoke and interpret results.

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 description coverage is 100%, so baseline is 3. The description adds value: for max_summary_chars, it explains the default, token equivalence, when to increase (for substantive bills), and the truncation check. For bill_id, it reiterates the source. This goes beyond the schema's own descriptions.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool's purpose: to get full bill detail given a bill_id. It specifies the exact return fields (sponsors, stage, title, summary, assent date) and distinguishes itself from the sibling tool 'bills_search_bills' by noting that the bill_id comes from that search tool.

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

Usage Guidelines4/5

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

The description explicitly says 'USE THIS TOOL WHEN you have a bill_id (from bills_search_bills) and want the full detail.' It also provides post-call guidance on using parliament_search_hansard or bills_search_bills for related queries. While it doesn't explicitly state when not to use it, the prerequisite condition is clear.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/paulieb89/uk-legal-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server