Skip to main content
Glama

Uk Contracts

by io.github.pipeworx-io

Generate llms.txt

generate_llms_txt
Read-onlyIdempotent

Generate a production-ready llms.txt file for any URL so AI crawlers (ChatGPT, Claude, Perplexity) can index the site cleanly. Fetches the page, extracts title/description/key links, and emits the standard llms.txt markdown format. Output is a single text blob ready to drop at site-root/llms.txt. Useful for: getting a client's site indexed by AI, drafting llms.txt for your own project, or auditing how an AI crawler would see a competitor.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYesFull URL of the site to summarize, e.g. "https://example.com" or a specific landing page.
max_linksNoMaximum number of link entries to include (default 25, max 50).

TDQS

A4.5/5.0
Behavior5/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint. The description adds meaningful process details: fetches page, extracts title/description/key links, emits standard markdown, and specifies output as a single text blob for site-root/llms.txt. 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?

The description is four sentences, each adding value: action, process, output format, and use cases. No fluff or repetition. Front-loaded with key 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?

Given the tool's simplicity (2 parameters, no output schema), the description covers purpose, process, output, and usage examples. Annotations provide safety context. It is fully adequate for agent invocation.

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% with both parameters described. The description provides an example for 'url' but adds no new semantic information beyond the schema's descriptions. Baseline 3 is 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?

The description clearly states the tool generates a production-ready llms.txt file for AI crawlers, specifying the verb 'Generate' and resource 'llms.txt file for any URL'. It distinguishes itself from sibling tools by focusing on a specific output format and use case.

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?

The description explicitly lists three use cases (getting a client's site indexed, drafting for own project, auditing competitor). While it does not mention when not to use, the positive guidance is strong and context-aware.

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