Skip to main content
Glama

Open Contracting

by io.github.pipeworx-io

Recent Alerts

recent_alerts
Read-onlyIdempotent

Pull fired events from your subscription feed. Returns the most recent alerts the evaluator has written to your persisted feed — each carries source, citation_uri (pipeworx:// when available), and the raw event payload. Filter by type (e.g. "sec_8k") and/or since (ISO timestamp). Set mark_read:true to flag returned events read so the next call only shows newer ones. Polls work fine; the same feed is also at GET registry.pipeworx.io/alerts.json for scripts and dashboards.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
typeNoOptional — filter to one subscription type.
limitNoMax events to return (1-200, default 50).
sinceNoOptional ISO timestamp — return events fired_at >= this time.
mark_readNoFlag the returned events read in the same call (default false).
unread_onlyNoReturn only events where read_at is null (default false).

TDQS

A4.5/5.0
Behavior5/5

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

Annotations provide readOnlyHint, idempotentHint, destructiveHint. Description adds key behavioral trait: setting mark_read:true flags events as read, changing state of persisted feed. It also mentions poll suitability and alternative endpoint, 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?

Description is 5 sentences covering purpose, return format, filters, mark_read behavior, and polling info. It is mostly concise but could be slightly more structured; still efficient.

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?

For a read tool without output schema, description adequately explains return fields and core behavior. It mentions alternative access method, which adds completeness. Some details like pagination are implied via limit parameter but not explicitly stated.

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% with descriptions. Description adds value by explaining behavior of mark_read (flag returned events read so next call shows only newer ones), default limit, and suggesting filter usage (e.g., 'sec_8k').

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 states 'Pull fired events from your subscription feed' with specific verb and resource. It details return fields (source, citation_uri, raw event payload) and filter options, clearly distinguishing from sibling tools like list_subscriptions which manage subscriptions.

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 explains when to use (pipeline alerts from a subscription feed) and notes that polling works fine, with an alternative endpoint for scripts. It doesn't explicitly state when not to use, but the context is clear.

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