Skip to main content
Glama

Open Contracting

by io.github.pipeworx-io

Oc Coverage

oc_coverage
Read-onlyIdempotent

Which open-contracting procurement data is currently available: per-country publisher name, release and contracting-process counts, and latest-release freshness. Call this first to learn which of the 18 covered countries (Albania, Croatia, Dominican Republic, Ghana, Guatemala, Honduras, Italy, Kenya, Kosovo, Liberia, Mexico/Oaxaca, Nigeria, Peru, Rwanda, Tanzania, Thailand/Bangkok, Uruguay, Zambia) have data, how much, and how current the data is before relying on it.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnly, openWorld, idempotent, and non-destructive behavior. The description adds meaningful context by specifying the data returned (publisher, counts, freshness), the set of 18 countries, and the recommended ordering. It does not introduce contradictions or omit significant behavioral details.

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 a single, informative sentence that front-loads the purpose and provides a useful country list. While the list is long, it is directly relevant to the tool's scope. It is not overly verbose and every part contributes to understanding the tool.

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 (no parameters, no output schema) and the presence of comprehensive annotations, the description is complete. It explains what data is returned, the geographic scope, and when to call the tool, leaving no critical gaps.

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?

The tool has zero parameters, so the schema and description do not need to explain parameter semantics. The baseline for no parameters is 4, and the description appropriately avoids over-explaining, making it easy to invoke.

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 function: it reports which open-contracting procurement data is available, including per-country publisher, counts, and freshness. It distinguishes itself from siblings by explicitly saying 'Call this first' to learn data availability before relying on it, making it a unique precursor tool.

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 provides explicit when-to-use guidance: 'Call this first to learn... before relying on it.' It implies the tool should be used before querying specific data, but does not name alternatives or when-not-to-use scenarios. This is clear context, though not fully exhaustive.

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

All Open Contracting 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.7/5.0
Disambiguation2/5

Several tool clusters overlap heavily: ask_pipeworx, ask_pipeworx_beta, ask_pipeworx_grounded, deep_research, discover_tools, and suggest_questions all serve query/discovery purposes; polymarket_edges, polymarket_arbitrage, polymarket_edge_tracker, polymarket_fill_risk, and bet_research all target prediction-market opportunity detection. ask_pipeworx_beta is explicitly identical to ask_pipeworx right now, making the distinction essentially invisible without deep description parsing.

Naming Consistency3/5

Names mix domain prefixes (oc_*, polymarket_*, pipeworx_*), action verbs (validate_claim, resolve_entity, generate_llms_txt), and plain nouns (entity_profile, recent_alerts, recent_changes). Most are readable snake_case, but there is no uniform verb_noun or domain-first convention, so the set feels stylistically fragmented rather than patterned.

Tool Count2/5

35 tools is a heavy surface for a server ostensibly named 'Open Contracting' — only 4 of the 35 tools actually relate to open contracting data. The rest sprawl across general data lookup, prediction markets, memory, subscriptions, npm scanning, and AI visibility, making the tool count feel bloated and unfocused relative to the stated purpose.

Completeness2/5

For the open-contracting domain implied by the server name, the surface is incomplete: there is coverage metadata, search, recent releases, and process history, but no direct retrieval of a single release by ID and no broader OCDS exploration tools. As a general data/Pipeworx toolkit the coverage is wide, but the severe mismatch between the server name and the actual tool set creates a significant gap between expectation and capability.

Resources