Skip to main content
Glama

search_bids

Search government bid opportunities (open and past) by keyword, state, and buyer level. Results are relevance-ranked; keyword matches in the title outrank passing mentions in the description. Optionally filter by set-aside program (set_asides).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "query": "<query>"
    },
    "name": "search_bids"
  }
}

Input Schema

NameRequiredDescriptionDefault
tierNoLevel of government buyer
queryYesKeywords, e.g. 'fiber optic' or 'cyber'
stateNoTwo-letter US state code, e.g. TX
open_onlyNotrue = only bids whose deadline has not passed
set_asidesNoSet-aside programs, any of which matches: SDVOSB, VOSB, HUBZone, 8(a), EDWOSB, WOSB, DVBE, DBE, MBE, WBE, SBE, HUB, SDB, SBS; 'none' = the record says no set-aside was used (unrestricted). Many records are not marked either way, so a set-aside search never returns them.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / set_asides
      Added value: +{
      +  "description": "Set-aside programs, any of which matches: SDVOSB, VOSB, HUBZone, 8(a), EDWOSB, WOSB, DVBE, DBE, MBE, WBE, SBE, HUB, SDB, SBS; 'none' = the record says no set-aside was used (unrestricted). Many records are not marked either way, so a set-aside search never returns them.",
      +  "items": {
      +    "enum": [
      +      "SDVOSB",
      +      "VOSB",
      +      "HUBZone",
      +      "8(a)",
      +      "EDWOSB",
      +      "WOSB",
      +      "DVBE",
      +      "DBE",
      +      "MBE",
      +      "WBE",
      +      "SBE",
      +      "HUB",
      +      "SDB",
      +      "SBS",
      +      "none"
      +    ],
      +    "type": "string"
      +  },
      +  "maxItems": 15,
      +  "type": "array"
      +}
  2. First observed

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden, and it does add real value: it discloses that results are relevance-ranked with title matches outranking body mentions, and it warns that unmarked set-aside records are excluded from set-aside searches. It omits result-size limits, pagination, and any output shape, which are significant gaps for a search tool with no output 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?

Three tight sentences, front-loaded with the resource and filters before the ranking and set-aside caveats. The only mild redundancy is the repeated set-aside filtering note, which already appears in the parameter schema.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

All five parameters are documented and the ranking model is explained, which is adequate for a five-parameter read-only search. However, with no output schema and no mention of return fields, result caps, or pagination, an agent cannot anticipate what a response will look like.

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 tier, query, state, open_only, and set_asides are all already documented, and the enum for set_asides is fully listed in the schema. The description's set-aside caveat largely restates the schema's own 'none' explanation and adds no syntax or format detail beyond it, so the 3 baseline is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Search government bid opportunities') plus the filterable dimensions (keyword, state, buyer level) and scope (open and past). This clearly distinguishes it from search_awards, but it never names a sibling to route against, so the differentiation is implied by the resource noun rather than stated.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied by the scope phrase '(open and past)' and the note that filters are optional, letting an agent infer that omitting filters broadens the search. There is no explicit when-to-use/when-not guidance or reference to alternatives like search_awards or get_recompete_radar, leaving routing decisions to inference.

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.

Resources