Skip to main content
Glama

search_awards

Filter federal contract awards by exact fields — recipient, awarding agency, NAICS code, state — instead of keyword search. Includes a single-bid filter for awards that drew exactly one offer. Use this when you know the slice you want; use get_award_history for topic/keyword search. Can filter by set-aside program (set_asides). amount: the award's current value; null = no current value reported (never the ceiling). Requires a BidCatch intel key.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "search_awards"
  }
}

Input Schema

NameRequiredDescriptionDefault
sortNorecent
naicsNoNAICS code, e.g. 541512
stateNoTwo-letter US state code, e.g. TX
agencyNoAwarding agency (partial match), e.g. 'Veterans Affairs'
recipientNoRecipient name (partial match), e.g. 'Lockheed'
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.
one_bid_onlyNotrue = only awards that received exactly one offer

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

A4.2/5.0
Behavior4/5

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

With no annotations, the description carries the burden well: it discloses the auth prerequisite ('Requires a BidCatch intel key'), the null semantics of the amount field ('null = no current value reported (never the ceiling)'), and the coverage gap on set-aside data. It does not cover result volume, pagination, or ordering behavior, which are the remaining behavioral unknowns.

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-loaded with the core purpose and the sibling routing in the first three sentences; the set-aside and amount notes follow logically. Slightly dense with em-dash asides and a repeated set-aside caveat already present in the schema, but nothing is wasted.

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?

For a 7-parameter, no-annotation, no-output-schema tool it covers purpose, routing, auth, and the trickiest field semantics. It omits anything about result counts, pagination, default sort behavior, or the shape of returned awards, which an agent would need before invoking it at scale.

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 already 86%, so most parameters are documented structurally, including the detailed set_asides enumeration text that the description largely repeats. The one genuine addition is the amount clarification, but amount is not even an input parameter (only a sort enum value), so it informs interpretation of results rather than parameter usage.

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 ('Filter federal contract awards'), names the exact filterable fields (recipient, awarding agency, NAICS, state), and explicitly contrasts with keyword search, so an agent can distinguish it from get_award_history and search_bids without opening a 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 an explicit when-to-use rule ('Use this when you know the slice you want') and names the alternative plus the condition that selects it ('use get_award_history for topic/keyword search'). It also warns that set-aside filtering silently excludes records not marked either way, which is a real usage caveat.

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