Skip to main content
Glama

Gov Auctions

by io.github.pipeworx-io

Discover Tools

discover_tools
Read-onlyIdempotent

Find tools by describing the data or task. Use when you need to browse, search, look up, or discover what tools exist for: SEC filings, financials, revenue, profit, FDA drugs, adverse events, FRED economic data, Census demographics, BLS jobs/unemployment/inflation, ATTOM real estate, ClinicalTrials, USPTO patents, weather, news, crypto, stocks. Returns the top-N most relevant tools with names, descriptions, and full input schemas (with curated examples) — each result is ready to call directly, no second schema lookup needed. Call this FIRST when you have many tools available and want to see the option set (not just one answer).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
qNoAlias for query.
taskNoAlias for query.
limitNoMaximum number of tools to return (default 20, max 50)
queryYesNatural language description of what you want to do (e.g., "analyze housing market trends", "look up FDA drug approvals", "find trade data between countries"). Accepts task, q, description, search as aliases.
searchNoAlias for query.
descriptionNoAlias for query.

Schema Changelog

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

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already provide readOnlyHint=true, idempotentHint=true, destructiveHint=false. The description adds valuable behavioral context: 'Returns the top-N most relevant tools with names, descriptions, and full input schemas (with curated examples) — each result is ready to call directly, no second schema lookup needed.' 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.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Description is front-loaded with purpose and usage, then output details. Every sentence adds value, though slightly long. Well-structured for clarity.

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 (discovery across many domains) and no output schema, the description is complete: it explains what it does, when to use it, what the return contains (top-N tools with schemas), and how to use the results. Sufficient 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%, so baseline is 3. The description does not add significant meaning beyond the schema; it mentions aliases but schema already covers them. No extra parameter depth.

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: 'Find tools by describing the data or task.' It lists numerous domains and explicitly differentiates itself from siblings by advising 'Call this FIRST when you have many tools available and want to see the option set (not just one answer).'

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 explicitly states when to use the tool: 'Use when you need to browse, search, look up, or discover what tools exist for: ...' and 'Call this FIRST when you have many tools available and want to see the option set (not just one answer).' This provides clear usage context and distinguishes from sibling tools.

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

All Gov Auctions 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 the same question-answering niche: ask_pipeworx, ask_pipeworx_beta (currently identical by its own description), ask_pipeworx_grounded, deep_research, and validate_claim are easy to confuse. The polymarket suite also has overlapping edge/arbitrage/fill-risk boundaries, and discover_tools/suggest_questions both serve onboarding. The verbose descriptions help, but the set as a whole creates real misselection risk.

Naming Consistency4/5

Most tools follow clear snake_case verb_noun or domain-prefix patterns (auctions_search, polymarket_edges, subscribe/unsubscribe, remember/recall/forget). Minor inconsistencies exist: auction_lot_details is singular while the auction group is plural, and polymarket_edges versus polymarket_edge_tracker breaks the prefix pattern slightly. Overall the naming is predictable and readable.

Tool Count2/5

36 tools is well above the 25-tool threshold and feels bloated for a server named 'Gov Auctions': only 5 tools actually concern auctions, while the rest are general Pipeworx research, prediction-market, memory, subscription, and utility tools. Even as a general data platform, the count is heavy and includes several overlapping meta-tools.

Completeness4/5

For the auction-specific surface, the set covers search, lot details, closing-soon, historical sold prices, and data coverage, which is a solid read-only lifecycle. The main gaps are non-critical: no auction-category browser, no auction-specific alert/subscription type, and no bidding workflow. The broad research/esolution tools fill in most adjacent data needs even if they dilute the server's stated focus.

Resources