Skip to main content
Glama

Legislation Uk

by io.github.pipeworx-io

Remember

remember
Idempotent

Save data the agent will need to reuse later — across this conversation or across sessions. Use when you discover something worth carrying forward (a resolved ticker, a target address, a user preference, a research subject) so you don't have to look it up again. Stored as a key-value pair scoped by your identifier. Authenticated users get persistent memory; anonymous sessions retain memory for 24 hours. Pair with recall to retrieve later, forget to delete.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
keyYesMemory key (e.g., "subject_property", "target_ticker", "user_preference")
valueYesValue to store (any text — findings, addresses, preferences, notes)

TDQS

A4.9/5.0
Behavior5/5

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

Adds context beyond annotations: memory scoped by identifier, 24-hour retention for anonymous users, overwrite behavior implied by idempotentHint. 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.

Conciseness5/5

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

Three sentences: purpose, usage, details. Front-loaded and no extraneous information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple key-value tool with 2 params and no output schema, description covers persistence, scope, and relation to siblings fully.

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%, but description adds value with key naming examples and explicit statement that value can be any text, aiding agent understanding.

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?

Uses specific verb 'save data' and resource 'key-value pair'. Clearly distinguishes from sibling tools 'recall' and 'forget' by naming them.

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 states when to use ('discover something worth carrying forward') and pairs with recall/forget. Provides scoping and persistence details for different user types.

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

All Legislation Uk 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

A3.8/5.0
Disambiguation2/5

The legislation-specific tools are distinct, but the server bundles dozens of unrelated Pipeworx/prediction-market/AI-visibility tools, making the set's purpose unclear. Several near-identical pairs exist: ask_pipeworx and ask_pipeworx_beta are explicitly identical right now, and ai_visibility_check overlaps heavily with scan_competitor_ai_presence. An agent would struggle to know which tool is the right entry point.

Naming Consistency2/5

Naming is mixed: snake_case dominates, but camelCase appears in ask_pipeworx, ask_pipeworx_grounded, generate_llms_txt, and pipeworx_feedback. There is also inconsistency in verb style — get_/search_/list_ coexist with bare verbs like remember, recall, forget, and subscribe. The legislation tools themselves follow a clean get_legislation* pattern, but the wider set does not.

Tool Count2/5

35 tools is too many for a server named 'Legislation Uk' where only 4 tools actually relate to UK legislation. The remaining 31 tools appear to belong to a broader data/prediction-market platform, which suggests severe scope creep or a mislabeled assembly. This bloats the surface area and makes the server harder for an agent to navigate.

Completeness4/5

For the stated UK-legislation purpose, the core read-and-search workflow is covered: search_legislation, get_legislation, get_legislation_section, and get_legislation_text together support discovery, metadata, targeted section lookup, and full-text retrieval with version selection. Obvious gaps remain, such as full-text content search and amendment/change history, but agents can complete the primary task of finding and reading legislation. The unrelated tools neither help nor complete this domain.

Resources