Skip to main content
Glama

Gov Auctions

by io.github.pipeworx-io

Remember

remember
Idempotent

Save data the agent will need to reuse later — across this conversation or across sessions. Use when you discover something worth carrying forward (a resolved ticker, a target address, a user preference, a research subject) so you don't have to look it up again. Stored as a key-value pair scoped by your identifier. Authenticated users get persistent memory; anonymous sessions retain memory for 24 hours. Pair with recall to retrieve later, forget to delete.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
keyYesMemory key (e.g., "subject_property", "target_ticker", "user_preference")
valueYesValue to store (any text — findings, addresses, preferences, notes)

Schema Changelog

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

  1. First observed

TDQS

A4.9/5.0
Behavior5/5

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

Description adds behavioral context beyond annotations (key-value pair scoped by identifier, persistence 24h for anonymous, authenticated users persistent). Consistent with idempotentHint=true.

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?

Concise multi-sentence structure with main purpose first, followed by usage guidance and pairing info. Every sentence adds value.

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?

Fully explains storage model, session scoping, and persistence. No gaps given the simple storage functionality and no output schema.

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 description adds contextual examples of key-value pairs (e.g., 'subject_property', 'target_ticker') that enhance understanding beyond schema.

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 verb ('save') and resource ('data'), provides concrete examples (resolved ticker, target address), and distinguishes from siblings (recall, forget).

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?

Explicitly indicates when to use ('when you discover something worth carrying forward'), contrasts with sibling tools, and notes authentication-based persistence differences.

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