Skip to main content
Glama
UK Parliament MCP Server

UK Parliament MCP Server

get_deposited_paper

Retrieve full details of a UK Parliament deposited paper by ID, including notes, attached documents, dates, corporate authors, and departments. Use after searching to read one paper completely.

Instructions

Get a deposited paper by id | deposited paper details, notes, attached documents, corporate authors | Use after search_deposited_papers to read one paper in full | Returns the paper with notes, attached document names, dates, authors and departments. See also: search_deposited_papers.

    Args:
        paper_id: Deposited paper id (paperId from search_deposited_papers).

    Returns:
        The deposited paper's full details.
    

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "paper_id": "<paper_id>"
    },
    "name": "get_deposited_paper"
  }
}

Input Schema

NameRequiredDescriptionDefault
paper_idYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.19.0

TDQS

A4.3/5.0
Behavior3/5

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

No annotations exist, so the description bears the full load. It discloses that this is a single-record read and what the record contains, but says nothing about behavior if the id is invalid, permission requirements, or rate limits. The 'Returns' section largely restates content already listed in the header and covered by the output schema.

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 purpose and routing hint in the first sentences, then structured Args/Returns sections. Slightly redundant: 'deposited paper details, notes, attached documents' in the header is repeated in the Returns line, and the output schema already supplies that.

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?

A one-parameter, output-schema-backed retrieval tool is well covered: purpose, sibling routing, parameter origin, and record contents are all present. Only missing pieces are error/failure behavior and explicit confirmation that no auth is required.

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 0%, so the description must compensate, and it does: it explains that paper_id is the 'paperId from search_deposited_papers', telling the agent where the value comes from and its provenance. It stops short of stating the type or expected range, but the origin hint is genuinely useful.

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 ('Get a deposited paper by id') and immediately enumerates the payload (notes, attached documents, corporate authors), which cleanly separates it from the sibling search_deposited_papers that returns many papers rather than one.

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 prescribes the workflow: 'Use after search_deposited_papers to read one paper in full', and names the alternative via 'See also: search_deposited_papers'. The agent knows both the trigger and the non-trigger context.

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

Deploy Server

Other Tools