Skip to main content
Glama
Sign In

UK Data for Agents

by uk.co.reliness
OverviewDiscussionsAdmin

bill_amendments

Read-onlyIdempotent

Lists the amendments tabled at one stage of a UK bill, with the clause or schedule targeted, the amendment wording, its sponsors and the decision recorded (agreed, negatived, withdrawn, not moved). For public affairs teams and campaigners tracking whether an amendment got through. Source: UK Parliament Bills API. Needs the bill ID and a stage_id from bill_stages_timeline; can filter by decision or a word in the amendment, and pages with skip. Decisions are null until Parliament records them. (cost: 1 credit)

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

Input Schema

NameRequiredDescriptionDefault
skipNointeger, optional, amendments to skip for paging, 0-100000, default 0
takeNointeger, optional, amendments to return 1-100, default 25
billIdNointeger, required, the Parliament bill ID, e.g. 4035
searchNostring, optional, word or phrase in the amendment text, e.g. ombudsman
decisionNostring, optional, only amendments with this recorded decision: agreed, agreed_on_division, withdrawn, withdrawn_before_debate, disagreed, negatived_on_division, not_moved, not_selected, not_called, no_decision, question_proposed, stood_part, not_stood_part, preempted; default all
billStageIdNointeger, required, the stage_id from bill_stages_timeline, e.g. 21180

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive), so the description's job is to add operational context — and it does: data source, a 1-credit cost, and the important caveat that decisions are null until Parliament records them. It does not describe pagination limits or default page size, which the schema carries instead.

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?

Front-loaded with the resource and its return shape, then prerequisites, then filters, then caveats — a sensible order. The audience sentence ('For public affairs teams and campaigners…') is the one line that is more positioning than instruction, though it is short.

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?

With six parameters and no output schema, the description compensates by summarizing what each amendment record contains and warning about null decisions. Only missing piece is pagination/response-shape detail, which is minor against an otherwise complete picture.

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 coverage is 100%, so the baseline is 3; the description exceeds it by adding provenance the schema lacks — that billStageId must come from bill_stages_timeline — and by framing skip as paging and decision/search as filters. It doesn't reconcile the mismatch between the schema's 'required' wording and the tool's reported 0 required parameters.

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?

States a specific verb and resource — lists amendments tabled at one stage of a UK bill — and enumerates the returned content (clause/schedule targeted, wording, sponsors, recorded decision). That scope is clearly distinct from siblings like bill_stages_timeline and bill_documents, so the agent can pick it without opening the schema.

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?

Names the prerequisites precisely and routes the agent to the correct sibling for the stage_id (bill_stages_timeline), plus explains the two filtering modes and paging. It stops short of stating exclusions (e.g. cross-stage or all-amendments queries), so it is strong context rather than a full when/when-not pair.

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

All UK Data for Agents toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources