Skip to main content
Glama
paulieb89

UK Legal Research MCP Server

Get Bill Detail

bills_get_bill
Read-onlyIdempotent

Retrieve full details of a UK bill by its ID, including sponsors, current stage, long title, summary, and Royal Assent date if enacted.

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
paramsYesBillDetailInput.

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
Behavior5/5

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

Beyond the annotations (readOnlyHint, idempotentHint), the description adds that summary text is capped by max_summary_chars and advises checking summary_truncated. This is valuable behavioral context not covered by annotations.

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 clear structure: usage instruction, return fields, after-calling suggestions. Every sentence is informative and earns its place.

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 output schema exists and the tool is a straightforward detail fetch, the description covers all necessary context: input source, output fields, important behavioral notes. Complete for an agent's needs.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Both parameters are fully described in the schema, but the description adds practical advice: bill_id comes from search results, max_summary_chars default and when to increase. This adds significant meaning beyond the schema.

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 purpose: to get detailed information about a bill given a bill_id from bills_search_bills. It lists specific return fields (sponsors, current stage, etc.), distinguishing it from the search sibling tool.

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

Usage Guidelines5/5

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

Explicitly tells when to use this tool, and provides after-calling guidance for related tools (parliament_search_hansard and bills_search_bills). This helps the agent choose appropriate follow-up actions.

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