Skip to main content
Glama

Uk Parliament

by io.github.pipeworx-io

Recall

recall
Read-onlyIdempotent

Retrieve a value previously saved via remember, or list all saved keys (omit the key argument). Use to look up context the agent stored earlier — the user's target ticker, an address, prior research notes — without re-deriving it from scratch. Scoped to your identifier (anonymous IP, BYO key hash, or account ID). Pair with remember to save, forget to delete.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
keyNoMemory key to retrieve (omit to list all keys)

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already indicate readOnly, idempotent, non-destructive. Description adds scoping info (by identifier) which is not in annotations. No contradictions.

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?

Three sentences, clear and front-loaded. Could be slightly more concise, but no extraneous information.

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 read tool with one parameter and rich annotations, the description covers purpose, usage, scoping, and pairing with siblings. No output schema needed.

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%. Description explains the key parameter's behavior (omit to list all keys), adding value beyond the schema's description.

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?

Clearly states the verb 'retrieve' and the resource 'a value previously saved via remember' or listing all keys. Distinguishes from sibling tools like 'remember' and 'forget' by referencing them.

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?

Explicitly says 'use to look up context the agent stored earlier' and mentions pairing with 'remember' and 'forget'. Does not explicitly state when not to use, but context is clear.

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

All Uk Parliament toolsInspect
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

B3.4/5.0
Disambiguation2/5

Several tools are near-duplicates (ask_pipeworx and ask_pipeworx_beta are currently identical; ai_visibility_check vs scan_competitor_ai_presence overlap), and the massive mix of unrelated domains (Polymarket betting, general data lookup, AI visibility) alongside UK Parliament tools makes selection confusing. An agent would struggle to know whether to use ask_pipeworx, ask_pipeworx_beta, or ask_pipeworx_grounded, or which of the five polymarket tools fits.

Naming Consistency3/5

Most tools use snake_case with readable names, but the action placement varies (verb_noun like get_bill vs noun_verb like bet_research, entity_profile), and there are compound names like generate_llms_txt and scan_competitor_ai_presence. The style is mostly consistent but the verb_noun pattern is not uniform across the set.

Tool Count2/5

38 tools is heavy, and the overwhelming majority are unrelated to the server's stated UK Parliament purpose. Only 7 tools (get_bill, search_bills, bill_stages, get_member, search_members, search_hansard, recent_divisions) have anything to do with Parliament, making the count wildly inappropriate for the apparent scope.

Completeness2/5

The Parliament-specific surface is thin: basic bill/member/Hansard lookups exist, but there are no tools for specific divisions/votes, committees, publications, or detailed procedural information. The vast non-Parliament tooling is irrelevant, creating a dead end for any real Parliament research beyond the basics.

Resources