Skip to main content
Glama
Sign In

Gov Bids

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Open Bids Search

open_bids_search
Read-onlyIdempotent

Find OPEN US government bid solicitations (RFPs/RFQs/IFBs) that vendors can currently respond to, from city & county procurement portals — updated daily. Filter by keyword (matches solicitation title/reference), jurisdiction, and closing window. Returns each opportunity with title, reference number, awarding jurisdiction, close date, and the URL to respond. By default returns OPEN bids sorted by soonest close date; set status to 'closed' or 'all' to search past solicitations too (we retain history). Use for 'what is <city/county> currently bidding out' or 'open RFPs for '. This is LIVE OPEN BIDS (for awarded contracts use gov_contracts_search).

Input Schema

NameRequiredDescriptionDefault
limitNoMax bids (default 25, max 100).
statusNoBid status (default 'open'). 'closed' / 'all' search retained history.
keywordNoCase-insensitive substring matched against the solicitation title/reference, e.g. "construction", "audit", "software".
jurisdictionNoJurisdiction key to target (e.g. "fort-worth-tx", "harris-county-tx", "cook-county-il"). Omit for all covered jurisdictions. Use gov_bids_jurisdictions to list keys.
closing_within_daysNoOnly OPEN bids closing within this many days from now.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "closing_within_days": 30,
+    "jurisdiction": "fort-worth-tx",
+    "keyword": "construction",
+    "limit": 25,
+    "status": "open"
+  },
+  {
+    "keyword": "software",
+    "limit": 50,
+    "status": "open"
+  }
+]
  2. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true, idempotentHint=true, destructiveHint=false. Beyond that, description adds that results are updated daily, sorted by soonest close date by default, returns specific fields, and retains history for closed/all status. No contradiction.

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 paragraph but well-structured: starts with primary purpose, then details filters, then default behavior and alternatives. It includes examples naturally. Could be slightly more concise, but all sentences earn their place.

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 no output schema, the description explicitly lists return fields (title, reference number, awarding jurisdiction, close date, URL). With 5 parameters all described and no required fields, the description covers defaults and usage patterns completely. No 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?

Schema description coverage is 100% (all 5 parameters described). Description adds value beyond schema by explaining that keyword matches solicitation title/reference, jurisdiction uses keys like 'fort-worth-tx', closing_within_days applies only to open bids, and limit has default 25 and max 100.

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 it finds open US government bid solicitations (RFPs/RFQs/IFBs) that vendors can respond to, from city & county procurement portals. It specifies the verb 'find' and the resource 'open bids', and distinguishes from sibling tool gov_contracts_search for awarded contracts.

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 says when to use (for open bids) and when not ('for awarded contracts use gov_contracts_search'). Provides example queries like 'what is <city/county> currently bidding out' and explains that status can be set to 'closed' or 'all' to search past solicitations.

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

All Gov Bids toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources