UK Parliament MCP Server

get_publication_types

Retrieve all publication types for UK bills to understand the document types associated with legislation.

Instructions

Get all publication types available for bills. Use when you need to understand the different types of documents that can be associated with legislation.

    Args:
        skip: Optional: number of records to skip (for pagination).
        take: Optional: number of records to return.

    Returns:
        All publication types with descriptions.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`skip`	No
`take`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Oct 6, 2026

TDQS

A3.6/5.0

Behavior3/5

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

No annotations are provided, so the description carries the burden. The word 'Get' and the fixed-return phrasing imply a safe read-only lookup, and it notes the response includes descriptions, but it says nothing about permissions, caching, or how many records are returned by default. Adequate for a trivial lookup but not rich.

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-loads the purpose, then a usage sentence, then a compact Args/Returns block. The Args section is somewhat redundant given the input schema, but overall it is tight and earns its place.

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?

For a simple two-param lookup with an output schema already describing the return shape, the description covers purpose, usage context, params, and the nature of the response. The only real gap is disambiguation from sibling type-listing tools.

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 0%, so the description must compensate, and it does: it documents skip as 'number of records to skip (for pagination)' and take as 'number of records to return.' This meaningfully clarifies the two bare integer params, though it doesn't give defaults or max values.

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

Purpose4/5

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

States a specific verb and resource ('Get all publication types available for bills') and scopes it to bills, which implicitly separates it from the similarly named sibling get_committee_publication_types. It stops short of naming that sibling explicitly, so it's clear but not fully differentiated.

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

Usage Guidelines3/5

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

'Use when you need to understand the different types of documents that can be associated with legislation' gives an implied context but no when-not guidance and no alternatives (e.g., get_committee_publication_types, bill_types). The usage cue is present but shallow.

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

Deploy Server