Skip to main content
Glama

Uk Contracts

by io.github.pipeworx-io

Recent Changes

recent_changes
Read-onlyIdempotent

"What's new with X" / "latest on Y" / "what happened to Z this week / month / quarter" / "updates on Acme" / "news on Tesla recently" / "what's happening with Apple" — change feed for a company in the last N days/weeks/months in ONE parallel call. Fans out to SEC EDGAR (filings since since), GDELT→GNews fallback (news mentions in window — GDELT preferred, GNews when rate-limited or 5xx), USPTO (patents granted; PatentsView API sunset May 2025 so this soft-fails until reactivated). since accepts ISO date ("2026-04-01") or relative shorthand ("7d", "30d", "3m", "1y"). Returns structured changes[] grouped by source + total_changes count + pipeworx:// citation URIs. Use entity_profile instead when you want the static profile (filings + fundamentals + LEI + patents) regardless of window.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
typeYesEntity type. Only "company" supported today.
sinceYesWindow start — ISO date ("2026-04-01") or relative ("7d", "30d", "3m", "1y"). Use "30d" or "1m" for typical monitoring.
valueYesTicker (e.g., "AAPL") or zero-padded CIK (e.g., "0000320193").

TDQS

A4.8/5.0
Behavior5/5

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

Beyond the annotations (readOnlyHint, idempotentHint, etc.), the description discloses parallel calls, fallback from GDELT to GNews, soft-fail for USPTO, and the window parameter behavior. No contradictions with 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?

The description is front-loaded with example queries, followed by technical detail. It is somewhat lengthy but every sentence adds valuable information. Could be slightly more concise, but well-structured.

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?

Given the tool's complexity (multiple data sources, parallel calls, fallback logic) and the lack of an output schema, the description comprehensively explains the return structure (changes[] grouped by source, total_changes count, citation URIs) and the behavior for each source. No gaps remain.

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 the description adds significant value: explains the 'since' parameter formats (ISO date, relative shorthand like '7d', '30d', '1y'), recommends typical values, and clarifies that 'value' can be a ticker or CIK. This goes beyond the schema descriptions.

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?

The description clearly states the tool's purpose: providing a change feed for a company (e.g., 'What's new with X') with a specific verb ('change feed') and resource ('company'). It distinguishes from the sibling 'entity_profile' by noting that entity_profile is for static profiles regardless of window.

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?

The description gives explicit usage context with example queries (e.g., 'latest on Y', 'what happened to Z this week') and directly states an alternative: 'Use entity_profile instead when you want the static profile...'. This clearly tells the agent when to use this tool vs. the sibling.

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 occupy nearly identical roles (ask_pipeworx, ask_pipeworx_beta, ask_pipeworx_grounded, deep_research, discover_tools), and ask_pipeworx_beta is explicitly the same router as ask_pipeworx. Company-data tools (entity_profile, compare_entities, recent_changes, validate_claim) and the Polymarket family also overlap heavily, making selection error-prone despite detailed descriptions.

Naming Consistency5/5

Tool names are consistently lowercase snake_case with a verb_noun pattern (search_notices, get_notice, find_a_tender_recent, validate_claim). Even longer names like polymarket_edge_tracker and ask_pipeworx_grounded follow a predictable style with no camelCase or mixed conventions.

Tool Count2/5

36 tools is already excessive for a focused server, and the 'Uk Contracts' name covers only five of them (search_notices, recent_notices, get_notice, find_a_tender_recent, find_a_tender_notice). The remaining 31 are unrelated Pipeworx/Polymarket/AI-marketing utilities, so the count badly mismatches the apparent scope.

Completeness4/5

For UK public procurement, the five relevant tools provide search, recent listing, and full-detail retrieval for both Contracts Finder and Find a Tender Service, covering the core workflows well. Minor gaps include no tender-specific alert/subscription support and no server-side keyword search for the high-value FTS feed.

Resources