Skip to main content
Glama

Datagov Uk

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)

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Description adds scoping details (anonymous IP, BYO key hash, account ID) beyond annotations, which already indicate read-only, idempotent, and non-destructive behavior. 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, each earning its place: purpose, usage context, scoping and pairing. No 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 one optional parameter, good annotations, and no output schema, description adequately covers behavior and return types (value or list of keys). Minor gap: no example return format.

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?

Single parameter 'key' is well-described, with schema covering 100%. Description adds the important note that omitting key lists all saved keys, enhancing schema info.

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?

Description clearly states it retrieves a saved value by key or lists all keys when omitted. Differentiates from siblings 'remember' and 'forget' by explicitly pairing with 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?

Provides clear use cases (look up stored context like ticker, address, notes) and mentions scoping, but lacks explicit when-not-to-use or alternatives.

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

All Datagov 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.6/5.0
Disambiguation3/5

Most tools have distinct purposes, but there is meaningful overlap among ask_pipeworx, ask_pipeworx_beta, ask_pipeworx_grounded, and deep_research, which all route questions to the same source catalog and could be easily confused. Similarly, ai_visibility_check and scan_competitor_ai_presence overlap, and the many polymarket_* tools require careful reading to distinguish. The descriptions are detailed enough to help, but the set is not cleanly separable.

Naming Consistency3/5

All names use lowercase snake_case, which is consistent in style, but the pattern is mixed: some tools use verb_noun (search_datasets, list_organizations, validate_claim), while others are bare nouns or noun phrases (entity_profile, dataset_details, recent_alerts, polymarket_edges). This makes the naming readable but not predictable, and it lacks a single clear convention.

Tool Count2/5

At 35 tools, this is a heavy surface, and most of them are unrelated to the server's apparent 'Datagov Uk' purpose—only search_datasets, dataset_details, list_organizations, and organization_details actually serve data.gov.uk. The rest are a general Pipeworx/prediction-market/AI-visibility toolkit bolted onto a government data server, making the count inappropriate for the stated scope.

Completeness2/5

For the nominal data.gov.uk domain, the four CKAN tools cover search, dataset details, and organization listing, but there is no create/update/delete (datasets are open data, so that is acceptable) and no direct resource download or preview helper despite resource links being returned. More importantly, the overwhelming majority of tools address unrelated domains, so the server's actual coverage is scattered and does not form a coherent complete surface for any single stated purpose.

Resources