UK Parliament MCP Server

get_cli_reference

Discover available parliament CLI commands and parameters by group or keyword, returning structured JSON details for each command.

Instructions

Get comprehensive CLI command reference | cli commands, terminal, command line, parliament command | Use to discover available CLI commands and their parameters | Returns JSON with command groups, names, descriptions, and parameters

    This tool helps LLMs understand what CLI commands are available in the
    `parliament` command-line tool, complementing the MCP tools.

    Args:
        group: Optional group name to filter (e.g., 'members', 'bills', 'votes').
               If not specified, returns all groups.
        search: Optional keyword to search across command names and descriptions.
                If specified, returns only matching commands.

    Returns:
        JSON with total_commands, total_groups, and groups array containing
        command details with parameters.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`group`	No
`search`	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.5/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 full burden. It does disclose the response shape and that it is a read-only reference ('Returns JSON with command groups, names, descriptions, and parameters'), which is useful. It omits any note on pagination, rate limits, or auth, though for a static reference tool the risk is low.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The leading pipe-separated keyword string ('cli commands, terminal, command line, parliament command') is keyword-stuffed filler, and the return-shape sentence is duplicated between the top line and the 'Returns' block. The Args section is efficient, but the overall payload has redundancy.

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 an output schema present, return values needn't be spelled out, yet the description still summarizes them. Both optional parameters are documented with defaults and examples, making it complete enough for an agent to call correctly.

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: 'group' is explained as a filter with concrete examples ('members', 'bills', 'votes') plus the default behavior when omitted, and 'search' is defined as a keyword match across command names and descriptions. This meaningfully exceeds the bare schema.

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 clear verb+resource: 'Get comprehensive CLI command reference' with explicit scope ('CLI commands... in the parliament command-line tool'). It distinguishes itself conceptually from the MCP data tools it complements, though it never names a specific sibling (e.g. parliament_guide) to route the agent.

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 to discover available CLI commands and their parameters' gives an implied use case, and 'complementing the MCP tools' hints at when it is relevant. However, it never states when NOT to use it or how it differs from related meta-tools like parliament_guide or parliament_workflow.

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

Deploy Server