UK Business Tools - Ledgerhall

Get Bill Detail

law_bills_get_bill

Read-onlyIdempotent

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

Name	Required	Description	Default
`bill_id`	Yes	Bill ID from bills_search_bills results.
`max_summary_chars`	No	Maximum 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

Name	Required	Description
`id`	Yes	Bill ID
`url`	Yes	Parliament URL for this bill
`is_act`	No	Whether the bill has received Royal Assent
`stages`	No	Legislative stages the bill has passed through
`summary`	No	Bill summary text, possibly truncated per max_summary_chars. Check summary_truncated and summary_original_length for full-text info.
`sponsors`	No	Bill sponsors
`long_title`	No	Full long title
`short_title`	Yes	Short title of the bill
`current_house`	No	House where the bill currently sits
`current_stage`	No	Current legislative stage
`originating_house`	No	House where the bill was introduced
`royal_assent_date`	No	Date Royal Assent was given
`summary_truncated`	No	True if summary was cut to fit max_summary_chars
`summary_original_length`	No	Original summary length in characters before any truncation

TDQS

A4.7/5.0

Behavior5/5

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

Annotations already declare readOnly, idempotent, and non-destructive. The description adds important behavioral context: summary text is capped per max_summary_chars and users should 'check summary_truncated in the response.' It also specifies the Royal Assent field is included 'if enacted,' clarifying conditional data presence.

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 tightly organized into three purposeful sections: when to use, what it returns, and next steps. Every sentence provides actionable information with no filler or redundancy.

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's simplicity (2 params, output schema present), the description fully covers usage context, return contents, truncation behavior, and downstream actions. No gap in understanding remains for the agent to invoke it correctly.

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% and parameter descriptions are already detailed (e.g., bill_id source, max_summary_chars default/range/truncation). The tool description reinforces that max_summary_chars caps summary length but adds no new semantic info 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 opens with 'USE THIS TOOL WHEN you have a bill_id (from bills_search_bills) and want the full detail,' which clearly states the verb (get), resource (bill detail), and prerequisite source of the ID. It further lists specific returned fields (sponsors, current stage, long title, summary, Royal Assent date), distinguishing it from the sibling 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 Guidelines5/5

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

Explicit 'USE THIS TOOL WHEN' identifies the exact condition for use. It also provides post-call guidance: 'AFTER calling, use parliament_search_hansard... or bills_search_bills... for adjacent bills,' effectively indicating alternatives and when not to use this tool (when seeking debates or related bills).

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

All UK Business Tools - Ledgerhall tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4/5.0

Disambiguation4/5

Tools are well-grouped by domain prefixes (dd_, gov_, law_, prop_) with clear descriptions that differentiate them. However, there is minor overlap, e.g., dd_search could be used instead of individual searches, and dd_fetch versus dedicated profile tools might cause confusion.

Naming Consistency5/5

All tools follow a consistent verb_noun pattern with domain-specific prefixes (dd_, gov_, law_, prop_). Names are descriptive and predictable, e.g., dd_charity_search, gov_govuk_search, law_bills_search_bills.

Tool Count4/5

70 tools is high but justified by the broad scope covering due diligence, government, legal, and property domains. Each domain has a reasonable number of tools (about 15-20 each). The count is on the upper end but still manageable.

Completeness5/5

The tool set is comprehensive across all domains: full CRUD for companies and charities, detailed legal research (cases, legislation, parliament, citations), property data (EPC, planning, price paid, rentals), and government information. No obvious gaps for the intended use cases.

Resources

Need Help?