Skip to main content
Glama

Uk Contracts

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)

Schema Changelog

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

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations show idempotent and non-destructive. Description adds persistence behavior (24-hour TTL for anonymous, persistent for authenticated) and scoping by identifier, going beyond annotations.

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?

Five sentences, each adding value. Well-structured with front-loaded purpose, clean explanation. Could be slightly more concise but effective.

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?

Describes storage semantics and pairing with recall/forget. No output schema, but not needed for a write tool. Complete enough for effective use.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so description adds little beyond schema. Schema already explains key and value, description only confirms key-value pair. Baseline 3 appropriate.

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 tool saves data for reuse across sessions, with specific verb 'save' and resource 'data'. Differentiates from sibling tools recall and forget.

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 when to use: when discovering something worth carrying forward. Mentions pairing with recall and forget, but no explicit when-not-to-use.

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

All Uk Contracts 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.9/5.0
Disambiguation2/5

Several tools are near-identical entry points: ask_pipeworx_beta explicitly matches ask_pipeworx exactly, ask_pipeworx_grounded only differs in grounded extraction, and deep_research overlaps with both. Company-research tools (entity_profile, compare_entities, recent_changes, validate_claim) and the Polymarket scanner family also have fuzzy boundaries despite long descriptions.

Naming Consistency3/5

All names are lowercase snake_case, which is a consistent base convention. However, the pattern mixes verb-first names (search_notices, get_notice, list_subscriptions), noun-first names (entity_profile, polymarket_edges, pipeworx_trending), and bare verbs (remember, recall, forget).

Tool Count2/5

At 36 tools, the server is well past the 25-tool threshold and feels like a platform dump rather than a scoped toolkit. Only about five tools actually serve the 'UK Contracts' name; the rest are general Pipeworx routing, Polymarket betting, memory, subscription, and AI-visibility utilities.

Completeness4/5

The UK procurement surface itself is solid: search_notices, recent_notices, and get_notice cover Contracts Finder, while find_a_tender_recent and find_a_tender_notice cover high-value Find a Tender notices. Minor gaps exist—notably no full-corpus keyword search for high-value Find a Tender notices, and Contracts Finder detail does not list documents—but agents can usually work around these.

Resources