Skip to main content
Glama

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).

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "limit": 25,
      "status": "open",
      "keyword": "construction",
      "jurisdiction": "fort-worth-tx",
      "closing_within_days": 30
    },
    "name": "open_bids_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.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint=false, so safety is covered; the description adds real context on top: data is refreshed daily, historical records are retained, and results default to open bids sorted by soonest close date. It stops short of stating pagination or rate-limit behavior, but the limit ceiling is documented in the schema.

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?

Front-loads what the tool returns, then filters, then defaults, then the sibling disambiguation — a sensible ordering. It is dense with useful detail rather than padded, though a few clauses (e.g. the RFPs/RFQs/IFBs parenthetical, the retention note) could be tightened slightly.

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?

With no output schema, the description compensates by enumerating returned fields (title, reference number, awarding jurisdiction, close date, response URL). Combined with the stated defaults, history retention, and sibling routing, an agent has everything needed to call and interpret this correctly.

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 description coverage is 100%, so all five parameters are already documented with examples and an enum for status. The description mostly restates the same filters (keyword matching title/reference, jurisdiction, closing window) and only adds the default sort ordering, which is modest added value over the 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?

States a specific verb and resource ('Find OPEN US government bid solicitations (RFPs/RFQs/IFBs)'), names the source (city & county procurement portals), and explicitly distinguishes itself from gov_contracts_search, which covers awarded contracts. An agent can tell exactly what this returns without opening the schema.

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?

Gives concrete when-to-use phrasing ('what is <city/county> currently bidding out', 'open RFPs for <keyword>') and routes the agent elsewhere for awarded contracts via gov_contracts_search, plus points to gov_bids_jurisdictions for jurisdiction keys. Both the alternative and the selecting condition are explicit.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.