Skip to main content
Glama

usaspending-mcp-server

Search Federal Awards

usaspending_search_awards
Read-onlyIdempotent

Search federal awards by keyword, recipient, agency, award type, NAICS code, assistance listing (CFDA) number, location, or date range. Returns ranked award summaries including recipient names, amounts, awarding agencies, and generated award IDs for use with usaspending_get_award; loan rows carry loan value, subsidy cost, and issue date in place of award amount and dates. Award types: A/B/C/D = contracts, IDV_A–IDV_E = IDVs, 02/03/04/05/F001/F002 = grants, 06/10/F006/F007 = direct payments, 07/08/F003/F004 = loans, 09/11/-1/F005/F008/F009/F010 = other assistance. Dates must be ISO 8601 (YYYY-MM-DD). Earliest data: 2007-10-01 via search API. DoD contracts have a 90-day publication lag.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNoPage number (1-based). Page-number pagination caps at a 50,000-result offset (page × limit), but the keyset cursor below is only returned while the offset stays under 10,000 — capture the cursor pair before paging past that, or the only way forward is page numbers.
sortNoSort field for results. Loans (07/08/F003/F004) sort by Loan Value, Subsidy Cost, Issued Date, Recipient Name, or Awarding Agency, defaulting to Loan Value. Every other group sorts by Award Amount, Total Outlays, Start Date, End Date, Recipient Name, or Awarding Agency, defaulting to Award Amount — except IDVs, which have no End Date. A sort the group does not support is rejected before the search runs.
limitNoMaximum results per page (1–100)
orderNoSort directiondesc
filtersNoOptional analytics-style filter object mirroring the shape the spending analytics tools accept, for reusing one filter set across tools. When both this object and the equivalent top-level flat filters are given, this object wins per-field. recipient_id is intentionally not accepted — this endpoint silently ignores it; filter by recipient via recipient_name.
keywordNoFull-text search across award descriptions, recipient names, and place names
agency_nameNoFilter to a specific awarding agency by name (e.g., "Department of Defense"). Use usaspending_autocomplete_filters type=awarding_agency to find exact names.
naics_codesNoFilter by NAICS industry codes (e.g., ["541512"]). Use usaspending_autocomplete_filters type=naics to look up codes.
time_periodNoFilter awards by date range (action date). Both blank means no date filter; one blank end is filled and named in the notice.
recipient_nameNoFilter by recipient name (partial match); maps to this endpoint's recipient_search_text. This endpoint has no recipient_id filter — use usaspending_search_recipients to look up a recipient by name.
location_filterNoFilter by place of performance location. Uses FIPS codes and 2-letter state abbreviations, not place names — use a geocoding server to resolve names to codes first.
award_type_codesNoFilter by award type codes. All codes must belong to a single group: A/B/C/D (contracts), IDV_A/IDV_B/IDV_B_A/IDV_B_B/IDV_B_C/IDV_C/IDV_D/IDV_E (IDVs), 02/03/04/05/F001/F002 (grants), 06/10/F006/F007 (direct payments), 07/08/F003/F004 (loans), 09/11/-1/F005/F008/F009/F010 (other assistance). Defaults to contracts. Mixing groups causes a 422 error. The group decides which sort values apply.
assistance_listingsNoFilter by Assistance Listing (CFDA) program numbers, e.g. ["93.866"]: two digits, a dot, then three digits or capital letters (11.67A). Matches an award when any of its listings equals one of these exactly; several values match any of them. A row's primary listing can differ from the one requested, and its amount is the whole award, not that listing's share. Assistance award types only — set award_type_codes to grants, direct payments, loans, or other assistance; contracts and IDVs carry no listings, so pairing them (including the default award_type_codes) is rejected. Use usaspending_autocomplete_filters type=cfda to look up numbers.
last_record_unique_idNoKeyset-pagination cursor: the last_record_unique_id from a prior response page_metadata. Provide together with last_record_sort_value.
last_record_sort_valueNoKeyset-pagination cursor: the last_record_sort_value from a prior response page_metadata. Provide together with last_record_unique_id to fetch the next page past the 50,000-result page-number cap. The upstream stops emitting the pair once page × limit reaches 10,000, so take it from a page below that offset. When both cursor fields are supplied, page is ignored.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
capNoPer-page cap (limit) applied to this page.
pageNoCurrent page number returned
errorNoPresent when the call failed. Absent on success.
shownNoNumber of awards returned on this page.
noticeNoHow to page on when more results may remain, which date bound was filled in when only the other was supplied, and — when results are empty — the applied filters with how to broaden. Absent when none applies.
resultsNoMatching award summaries
has_nextNoWhether more results may remain — set on a full page even when the upstream flag reports none.
truncatedNoTrue when this page was capped at `limit` and more results may remain (continue via page or the cursor).
page_metadataNoPagination metadata. This endpoint does not return a total match count; use has_next and the cursor pair to page.
applied_keywordNoKeyword filter applied to this search
upstream_messagesNoNotices the USAspending API returned with this response — e.g. a supplied filter it ignored because this endpoint does not support it. Every successful response also carries a standing advisory that search covers 2007-10-01 onward; that advisory is boilerplate, not a verdict on the dates requested. Present whenever the API returns any messages.
applied_agency_nameNoAwarding agency name filter applied
applied_naics_codesNoNAICS codes filter applied (comma-separated)
applied_time_period_endNoEnd of the date range sent (YYYY-MM-DD), including a filled-in end
applied_time_period_startNoStart of the date range sent (YYYY-MM-DD), including a filled-in start
applied_assistance_listingsNoAssistance Listing numbers filter applied (comma-separated)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed29 schema fields changed
    • addedInput schema / properties / assistance_listings
      Added value: +{
      +  "description": "Filter by Assistance Listing (CFDA) program numbers, e.g. [\"93.866\"]: two digits, a dot, then three digits or capital letters (11.67A). Matches an award when any of its listings equals one of these exactly; several values match any of them. A row's primary listing can differ from the one requested, and its amount is the whole award, not that listing's share. Assistance award types only — set award_type_codes to grants, direct payments, loans, or other assistance; contracts and IDVs carry no listings, so pairing them (including the default award_type_codes) is rejected. Use usaspending_autocomplete_filters type=cfda to look up numbers.",
      +  "items": {
      +    "description": "Assistance Listing number, e.g. 93.866",
      +    "pattern": "^\\d{2}\\.[0-9A-Z]{3}$",
      +    "type": "string"
      +  },
      +  "type": "array"
      +}
    • changedInput schema / properties / award_type_codes / description
      Previous value: -"Filter by award type codes. All codes must belong to a single group: A/B/C/D (contracts), 02/03/04/05 (grants), 06/10 (direct payments), 07/08 (loans), IDV_A–IDV_E (IDVs). Defaults to contracts. Mixing groups across categories causes a 422 error."New value: +"Filter by award type codes. All codes must belong to a single group: A/B/C/D (contracts), IDV_A/IDV_B/IDV_B_A/IDV_B_B/IDV_B_C/IDV_C/IDV_D/IDV_E (IDVs), 02/03/04/05/F001/F002 (grants), 06/10/F006/F007 (direct payments), 07/08/F003/F004 (loans), 09/11/-1/F005/F008/F009/F010 (other assistance). Defaults to contracts. Mixing groups causes a 422 error. The group decides which sort values apply."
    • addedInput schema / properties / award_type_codes / minItems
      Added value: +1
    • changedInput schema / properties / filters / properties / award_type_codes / description
      Previous value: -"Award type codes; all must belong to one group (A/B/C/D, 02/03/04/05, 06/10, 07/08, IDV_A–IDV_E)"New value: +"Award type codes; all must belong to one group (A/B/C/D contracts, IDV_A–IDV_E IDVs, 02/03/04/05/F001/F002 grants, 06/10/F006/F007 direct payments, 07/08/F003/F004 loans, 09/11/-1/F005/F008/F009/F010 other assistance). When non-empty, overrides the top-level award_type_codes and decides which sort values apply; an empty array falls back to the top-level value."
    • addedInput schema / properties / filters / properties / time_period_end / anyOf
      Added value: +[
      +  {
      +    "const": "",
      +    "type": "string"
      +  },
      +  {
      +    "description": "Date as YYYY-MM-DD; month and day may be unpadded",
      +    "pattern": "^\\d{4}-\\d{1,2}-\\d{1,2}$",
      +    "type": "string"
      +  }
      +]
    • changedInput schema / properties / filters / properties / time_period_end / description
      Previous value: -"End date (YYYY-MM-DD). Requires time_period_start."New value: +"End date (YYYY-MM-DD). Given alone, the range starts at 2007-10-01, the earliest searchable date."
    • removedInput schema / properties / filters / properties / time_period_end / type
      Removed value: -"string"
    • addedInput schema / properties / filters / properties / time_period_start / anyOf
      Added value: +[
      +  {
      +    "const": "",
      +    "type": "string"
      +  },
      +  {
      +    "description": "Date as YYYY-MM-DD; month and day may be unpadded",
      +    "pattern": "^\\d{4}-\\d{1,2}-\\d{1,2}$",
      +    "type": "string"
      +  }
      +]
    • changedInput schema / properties / filters / properties / time_period_start / description
      Previous value: -"Start date (YYYY-MM-DD); earliest valid 2007-10-01. Requires time_period_end."New value: +"Start date (YYYY-MM-DD); earliest valid 2007-10-01. Given alone, the range runs through today (UTC)."
    • removedInput schema / properties / filters / properties / time_period_start / type
      Removed value: -"string"
    • removedInput schema / properties / sort / default
      Removed value: -"Award Amount"
    • changedInput schema / properties / sort / description
      Previous value: -"Sort field for results"New value: +"Sort field for results. Loans (07/08/F003/F004) sort by Loan Value, Subsidy Cost, Issued Date, Recipient Name, or Awarding Agency, defaulting to Loan Value. Every other group sorts by Award Amount, Total Outlays, Start Date, End Date, Recipient Name, or Awarding Agency, defaulting to Award Amount — except IDVs, which have no End Date. A sort the group does not support is rejected before the search runs."
    • changedInput schema / properties / sort / enum
      Previous value: -[
      -  "Award Amount",
      -  "Total Outlays",
      -  "Start Date",
      -  "End Date",
      -  "Recipient Name",
      -  "Awarding Agency"
      -]New value: +[
      +  "Award Amount",
      +  "Total Outlays",
      +  "Start Date",
      +  "End Date",
      +  "Loan Value",
      +  "Subsidy Cost",
      +  "Issued Date",
      +  "Recipient Name",
      +  "Awarding Agency"
      +]
    • changedInput schema / properties / time_period / description
      Previous value: -"Filter awards by date range (action date)"New value: +"Filter awards by date range (action date). Both blank means no date filter; one blank end is filled and named in the notice."
    • addedInput schema / properties / time_period / properties / end_date / anyOf
      Added value: +[
      +  {
      +    "const": "",
      +    "type": "string"
      +  },
      +  {
      +    "description": "Date as YYYY-MM-DD; month and day may be unpadded",
      +    "pattern": "^\\d{4}-\\d{1,2}-\\d{1,2}$",
      +    "type": "string"
      +  }
      +]
    • changedInput schema / properties / time_period / properties / end_date / description
      Previous value: -"End date in ISO 8601 format (YYYY-MM-DD)"New value: +"End date in ISO 8601 format (YYYY-MM-DD). Blank (\"\") leaves the end open, filled with today (UTC)."
    • removedInput schema / properties / time_period / properties / end_date / type
      Removed value: -"string"
    • addedInput schema / properties / time_period / properties / start_date / anyOf
      Added value: +[
      +  {
      +    "const": "",
      +    "type": "string"
      +  },
      +  {
      +    "description": "Date as YYYY-MM-DD; month and day may be unpadded",
      +    "pattern": "^\\d{4}-\\d{1,2}-\\d{1,2}$",
      +    "type": "string"
      +  }
      +]
    • changedInput schema / properties / time_period / properties / start_date / description
      Previous value: -"Start date in ISO 8601 format (YYYY-MM-DD); earliest valid: 2007-10-01"New value: +"Start date in ISO 8601 format (YYYY-MM-DD); earliest valid: 2007-10-01. Blank (\"\") leaves the start open, filled with 2007-10-01."
    • removedInput schema / properties / time_period / properties / start_date / type
      Removed value: -"string"
    • addedOutput schema / properties / applied_assistance_listings
      Added value: +{
      +  "description": "Assistance Listing numbers filter applied (comma-separated)",
      +  "type": "string"
      +}
    • changedOutput schema / properties / applied_time_period_end / description
      Previous value: -"End date filter applied (YYYY-MM-DD)"New value: +"End of the date range sent (YYYY-MM-DD), including a filled-in end"
    • changedOutput schema / properties / applied_time_period_start / description
      Previous value: -"Start date filter applied (YYYY-MM-DD)"New value: +"Start of the date range sent (YYYY-MM-DD), including a filled-in start"
    • changedOutput schema / properties / error / properties / data / properties / reason / description
      Previous value: -"Machine-readable failure mode. Declared by this tool: `api_unavailable`: USAspending.gov API is unreachable or returns an error. `api_timeout`: USAspending.gov did not respond before the request deadline elapsed. `pagination_limit_exceeded`: page multiplied by limit exceeds the endpoint 50,000-result page window and no cursor was supplied. `date_before_earliest`: The resolved start date precedes the 2007-10-01 earliest date this endpoint can search. Other values are possible when a failure originates below the handler."New value: +"Machine-readable failure mode. Declared by this tool: `api_unavailable`: USAspending.gov API is unreachable or returns an error. `api_timeout`: USAspending.gov did not respond before the request deadline elapsed. `pagination_limit_exceeded`: page multiplied by limit exceeds the endpoint 50,000-result page window and no cursor was supplied. `date_before_earliest`: The resolved start date precedes the 2007-10-01 earliest date this endpoint can search. `date_range_inverted`: Both ends of the date range were supplied and the start date falls after the end date. `unsupported_sort`: The sort value is not one the award type group supports. `assistance_listings_type_mismatch`: assistance_listings was given while the award type codes include contract or IDV codes, or were left at the contract default. Other values are possible when a failure originates below the handler."
    • changedOutput schema / properties / error / properties / data / properties / reason / examples
      Previous value: -[
      -  "api_unavailable",
      -  "api_timeout",
      -  "pagination_limit_exceeded",
      -  "date_before_earliest"
      -]New value: +[
      +  "api_unavailable",
      +  "api_timeout",
      +  "pagination_limit_exceeded",
      +  "date_before_earliest",
      +  "date_range_inverted",
      +  "unsupported_sort",
      +  "assistance_listings_type_mismatch"
      +]
    • changedOutput schema / properties / notice / description
      Previous value: -"Recovery hint when results are empty — echoes applied filters and suggests how to broaden. Absent when results are present."New value: +"How to page on when more results may remain, which date bound was filled in when only the other was supplied, and — when results are empty — the applied filters with how to broaden. Absent when none applies."
    • addedOutput schema / properties / results / items / properties / issued_date
      Added value: +{
      +  "description": "Date the loan was issued (YYYY-MM-DD; loans only — they carry no start or end date)",
      +  "type": "string"
      +}
    • addedOutput schema / properties / results / items / properties / loan_value
      Added value: +{
      +  "description": "Face value of the loan in USD (loans only — they carry no award_amount)",
      +  "type": "number"
      +}
    • addedOutput schema / properties / results / items / properties / subsidy_cost
      Added value: +{
      +  "description": "Original subsidy cost of the loan in USD — the estimated long-term cost to the government (loans only)",
      +  "type": "number"
      +}
  2. Changed6 schema fields changed
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
    • addedInput schema / additionalProperties
      Added value: +false
    • changedOutput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
    • addedOutput schema / anyOf
      Added value: +[
      +  {
      +    "not": {
      +      "required": [
      +        "error"
      +      ]
      +    },
      +    "required": [
      +      "results",
      +      "page_metadata",
      +      "page",
      +      "has_next"
      +    ]
      +  },
      +  {
      +    "required": [
      +      "error"
      +    ]
      +  }
      +]
    • addedOutput schema / properties / error
      Added value: +{
      +  "additionalProperties": {},
      +  "description": "Present when the call failed. Absent on success.",
      +  "properties": {
      +    "code": {
      +      "description": "JSON-RPC error code for this failure.",
      +      "maximum": 9007199254740991,
      +      "minimum": -9007199254740991,
      +      "type": "integer"
      +    },
      +    "data": {
      +      "additionalProperties": {},
      +      "properties": {
      +        "reason": {
      +          "description": "Machine-readable failure mode. Declared by this tool: `api_unavailable`: USAspending.gov API is unreachable or returns an error. `api_timeout`: USAspending.gov did not respond before the request deadline elapsed. `pagination_limit_exceeded`: page multiplied by limit exceeds the endpoint 50,000-result page window and no cursor was supplied. `date_before_earliest`: The resolved start date precedes the 2007-10-01 earliest date this endpoint can search. Other values are possible when a failure originates below the handler.",
      +          "examples": [
      +            "api_unavailable",
      +            "api_timeout",
      +            "pagination_limit_exceeded",
      +            "date_before_earliest"
      +          ],
      +          "type": "string"
      +        },
      +        "recovery": {
      +          "additionalProperties": {},
      +          "description": "Actionable next step for the caller.",
      +          "properties": {
      +            "hint": {
      +              "type": "string"
      +            }
      +          },
      +          "required": [
      +            "hint"
      +          ],
      +          "type": "object"
      +        },
      +        "retryable": {
      +          "description": "Whether retrying may succeed.",
      +          "type": "boolean"
      +        }
      +      },
      +      "type": "object"
      +    },
      +    "message": {
      +      "description": "Human-readable description of what went wrong.",
      +      "type": "string"
      +    }
      +  },
      +  "required": [
      +    "code",
      +    "message"
      +  ],
      +  "type": "object"
      +}
    • removedOutput schema / required
      Removed value: -[
      -  "results",
      -  "page_metadata",
      -  "page",
      -  "has_next"
      -]
  3. Changed2 schema fields changed
    • changedInput schema / properties / agency_name / description
      Previous value: -"Filter to a specific awarding agency by name (e.g., \"Department of Defense\"). Use usaspending_autocomplete type=awarding_agency to find exact names."New value: +"Filter to a specific awarding agency by name (e.g., \"Department of Defense\"). Use usaspending_autocomplete_filters type=awarding_agency to find exact names."
    • changedInput schema / properties / naics_codes / description
      Previous value: -"Filter by NAICS industry codes (e.g., [\"541512\"]). Use usaspending_autocomplete type=naics to look up codes."New value: +"Filter by NAICS industry codes (e.g., [\"541512\"]). Use usaspending_autocomplete_filters type=naics to look up codes."
  4. Changed7 schema fields changed
    • changedInput schema / properties / last_record_sort_value / description
      Previous value: -"Keyset-pagination cursor: the last_record_sort_value from a prior response page_metadata. Provide together with last_record_unique_id to fetch the next page past the 50,000-result page-number cap. When both cursor fields are supplied, page is ignored."New value: +"Keyset-pagination cursor: the last_record_sort_value from a prior response page_metadata. Provide together with last_record_unique_id to fetch the next page past the 50,000-result page-number cap. The upstream stops emitting the pair once page × limit reaches 10,000, so take it from a page below that offset. When both cursor fields are supplied, page is ignored."
    • changedInput schema / properties / page / description
      Previous value: -"Page number (1-based). Page-number pagination caps at a 50,000-result offset (page × limit); to read past that, use the cursor fields below."New value: +"Page number (1-based). Page-number pagination caps at a 50,000-result offset (page × limit), but the keyset cursor below is only returned while the offset stays under 10,000 — capture the cursor pair before paging past that, or the only way forward is page numbers."
    • changedOutput schema / properties / has_next / description
      Previous value: -"Whether there are more pages of results"New value: +"Whether more results may remain — set on a full page even when the upstream flag reports none."
    • changedOutput schema / properties / page_metadata / properties / has_next / description
      Previous value: -"Whether there are more pages of results"New value: +"Whether more results may remain — true on a full page even when the upstream flag reports none, since this endpoint under-reports continuation on a final full page and on every page past a 10,000-result offset. A short or empty page marks the end."
    • changedOutput schema / properties / page_metadata / properties / last_record_sort_value / description
      Previous value: -"Keyset-pagination cursor for the next page — pass back as last_record_sort_value to continue past the 50,000-result page limit"New value: +"Keyset-pagination cursor for the next page — pass back as last_record_sort_value to continue past the 50,000-result page limit. Absent once page × limit reaches 10,000, where the upstream stops emitting the pair."
    • changedOutput schema / properties / page_metadata / properties / last_record_unique_id / description
      Previous value: -"Keyset-pagination cursor for the next page — pass back as last_record_unique_id alongside last_record_sort_value"New value: +"Keyset-pagination cursor for the next page — pass back as last_record_unique_id alongside last_record_sort_value. Absent on the same pages that omit last_record_sort_value."
    • changedOutput schema / properties / truncated / description
      Previous value: -"True when this page was capped at `limit` and more results remain (continue via page or the cursor)."New value: +"True when this page was capped at `limit` and more results may remain (continue via page or the cursor)."
  5. Changed1 schema field changed
    • changedOutput schema / properties / upstream_messages / description
      Previous value: -"Notices the USAspending API returned for this request — e.g. a supplied filter that was ignored because this endpoint does not support it, or the 2007-10-01 date-floor note. Present whenever the API returns any messages."New value: +"Notices the USAspending API returned with this response — e.g. a supplied filter it ignored because this endpoint does not support it. Every successful response also carries a standing advisory that search covers 2007-10-01 onward; that advisory is boilerplate, not a verdict on the dates requested. Present whenever the API returns any messages."
  6. Changed15 schema fields changed
    • addedInput schema / properties / filters
      Added value: +{
      +  "description": "Optional analytics-style filter object mirroring the shape the spending analytics tools accept, for reusing one filter set across tools. When both this object and the equivalent top-level flat filters are given, this object wins per-field. recipient_id is intentionally not accepted — this endpoint silently ignores it; filter by recipient via recipient_name.",
      +  "properties": {
      +    "agency_name": {
      +      "description": "Awarding agency name (toptier), e.g., \"Department of Defense\"",
      +      "type": "string"
      +    },
      +    "award_type_codes": {
      +      "description": "Award type codes; all must belong to one group (A/B/C/D, 02/03/04/05, 06/10, 07/08, IDV_A–IDV_E)",
      +      "items": {
      +        "type": "string"
      +      },
      +      "type": "array"
      +    },
      +    "keywords": {
      +      "description": "Full-text search terms across award descriptions, recipient names, and places",
      +      "items": {
      +        "type": "string"
      +      },
      +      "type": "array"
      +    },
      +    "naics_codes": {
      +      "description": "NAICS industry codes to require, e.g., [\"541512\"]",
      +      "items": {
      +        "type": "string"
      +      },
      +      "type": "array"
      +    },
      +    "recipient_name": {
      +      "description": "Recipient name search (partial match); maps to recipient_search_text. Use instead of recipient_id, which this endpoint ignores.",
      +      "type": "string"
      +    },
      +    "time_period_end": {
      +      "description": "End date (YYYY-MM-DD). Requires time_period_start.",
      +      "type": "string"
      +    },
      +    "time_period_start": {
      +      "description": "Start date (YYYY-MM-DD); earliest valid 2007-10-01. Requires time_period_end.",
      +      "type": "string"
      +    }
      +  },
      +  "type": "object"
      +}
    • addedInput schema / properties / last_record_sort_value
      Added value: +{
      +  "description": "Keyset-pagination cursor: the last_record_sort_value from a prior response page_metadata. Provide together with last_record_unique_id to fetch the next page past the 50,000-result page-number cap. When both cursor fields are supplied, page is ignored.",
      +  "type": "string"
      +}
    • addedInput schema / properties / last_record_unique_id
      Added value: +{
      +  "description": "Keyset-pagination cursor: the last_record_unique_id from a prior response page_metadata. Provide together with last_record_sort_value.",
      +  "maximum": 9007199254740991,
      +  "minimum": -9007199254740991,
      +  "type": "integer"
      +}
    • changedInput schema / properties / page / description
      Previous value: -"Page number (1-based)"New value: +"Page number (1-based). Page-number pagination caps at a 50,000-result offset (page × limit); to read past that, use the cursor fields below."
    • changedInput schema / properties / recipient_name / description
      Previous value: -"Filter by recipient name (partial match). Use usaspending_search_recipients for precise recipient_id filtering."New value: +"Filter by recipient name (partial match); maps to this endpoint's recipient_search_text. This endpoint has no recipient_id filter — use usaspending_search_recipients to look up a recipient by name."
    • addedOutput schema / properties / cap
      Added value: +{
      +  "description": "Per-page cap (limit) applied to this page.",
      +  "type": "number"
      +}
    • changedOutput schema / properties / page_metadata / description
      Previous value: -"Pagination metadata"New value: +"Pagination metadata. This endpoint does not return a total match count; use has_next and the cursor pair to page."
    • addedOutput schema / properties / page_metadata / properties / last_record_sort_value
      Added value: +{
      +  "description": "Keyset-pagination cursor for the next page — pass back as last_record_sort_value to continue past the 50,000-result page limit",
      +  "type": "string"
      +}
    • addedOutput schema / properties / page_metadata / properties / last_record_unique_id
      Added value: +{
      +  "description": "Keyset-pagination cursor for the next page — pass back as last_record_unique_id alongside last_record_sort_value",
      +  "type": "number"
      +}
    • removedOutput schema / properties / page_metadata / properties / total
      Removed value: -{
      -  "description": "Total number of matching awards",
      -  "type": "number"
      -}
    • addedOutput schema / properties / results / items / properties / agency_slug
      Added value: +{
      +  "description": "URL-friendly awarding-agency slug (e.g., national-aeronautics-and-space-administration) — pass to usaspending_get_agency as agency_slug. Absent when the agency has no profile page.",
      +  "type": "string"
      +}
    • addedOutput schema / properties / shown
      Added value: +{
      +  "description": "Number of awards returned on this page.",
      +  "type": "number"
      +}
    • removedOutput schema / properties / totalCount
      Removed value: -{
      -  "description": "Total number of matching awards across all pages (when available)",
      -  "type": "number"
      -}
    • addedOutput schema / properties / truncated
      Added value: +{
      +  "description": "True when this page was capped at `limit` and more results remain (continue via page or the cursor).",
      +  "type": "boolean"
      +}
    • addedOutput schema / properties / upstream_messages
      Added value: +{
      +  "description": "Notices the USAspending API returned for this request — e.g. a supplied filter that was ignored because this endpoint does not support it, or the 2007-10-01 date-floor note. Present whenever the API returns any messages.",
      +  "items": {
      +    "type": "string"
      +  },
      +  "type": "array"
      +}
  7. Changed2 schema fields changed
    • removedOutput schema / properties / total
      Removed value: -{
      -  "description": "Total number of matching awards across all pages (when available)",
      -  "type": "number"
      -}
    • addedOutput schema / properties / totalCount
      Added value: +{
      +  "description": "Total number of matching awards across all pages (when available)",
      +  "type": "number"
      +}
  8. Changed7 schema fields changed
    • removedInput schema / properties / naics_code
      Removed value: -{
      -  "description": "Filter by NAICS industry code (e.g., \"541512\"). Use usaspending_autocomplete type=naics to look up codes.",
      -  "type": "string"
      -}
    • addedInput schema / properties / naics_codes
      Added value: +{
      +  "description": "Filter by NAICS industry codes (e.g., [\"541512\"]). Use usaspending_autocomplete type=naics to look up codes.",
      +  "items": {
      +    "type": "string"
      +  },
      +  "type": "array"
      +}
    • addedOutput schema / properties / applied_agency_name
      Added value: +{
      +  "description": "Awarding agency name filter applied",
      +  "type": "string"
      +}
    • addedOutput schema / properties / applied_keyword
      Added value: +{
      +  "description": "Keyword filter applied to this search",
      +  "type": "string"
      +}
    • addedOutput schema / properties / applied_naics_codes
      Added value: +{
      +  "description": "NAICS codes filter applied (comma-separated)",
      +  "type": "string"
      +}
    • addedOutput schema / properties / applied_time_period_end
      Added value: +{
      +  "description": "End date filter applied (YYYY-MM-DD)",
      +  "type": "string"
      +}
    • addedOutput schema / properties / applied_time_period_start
      Added value: +{
      +  "description": "Start date filter applied (YYYY-MM-DD)",
      +  "type": "string"
      +}
  9. Changed6 schema fields changed
    • addedOutput schema / properties / has_next
      Added value: +{
      +  "description": "Whether there are more pages of results",
      +  "type": "boolean"
      +}
    • removedOutput schema / properties / message
      Removed value: -{
      -  "description": "Recovery hint when results are empty — echoes applied filters and suggests how to broaden. Absent when results are present.",
      -  "type": "string"
      -}
    • addedOutput schema / properties / notice
      Added value: +{
      +  "description": "Recovery hint when results are empty — echoes applied filters and suggests how to broaden. Absent when results are present.",
      +  "type": "string"
      +}
    • addedOutput schema / properties / page
      Added value: +{
      +  "description": "Current page number returned",
      +  "type": "number"
      +}
    • addedOutput schema / properties / total
      Added value: +{
      +  "description": "Total number of matching awards across all pages (when available)",
      +  "type": "number"
      +}
    • changedOutput schema / required
      Previous value: -[
      -  "results",
      -  "page_metadata"
      -]New value: +[
      +  "results",
      +  "page_metadata",
      +  "page",
      +  "has_next"
      +]
  10. First observed

TDQS

A4.3/5.0
Behavior5/5

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

Annotations already mark the tool as read-only, idempotent, and open-world, and the description adds valuable non-obvious behavior: ranked award summaries, loan-specific field substitutions, award type group meanings, ISO 8601 date requirements, the 2007-10-01 data floor, and the 90-day DoD publication lag. This goes well beyond the structured annotations and materially helps the agent anticipate results.

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?

The description is compact yet information-dense: each sentence carries a distinct fact, from search dimensions and return payload shape to award type codes, date constraints, and data lag. It is front-loaded with the core purpose and contains no filler.

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?

For a tool with 15 parameters, a full output schema, and safety annotations, the description covers the highest-risk behavioral constraints—date floor, DoD lag, loan row differences, and award type grouping—while the schema handles pagination, defaults, and parameter-level details. Nothing essential for selecting or invoking the tool is missing.

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%, with every parameter already documented in detail, including nested filters, cursors, and constraints. The description adds orienting context about award type codes and date formats, but it does not introduce new parameter-level semantics beyond what the schema already contains.

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 names a specific verb ('Search federal awards') and enumerates the major search dimensions: keyword, recipient, agency, award type, NAICS, CFDA, location, and date range. It also states that the result includes generated award IDs for use with usaspending_get_award, which clearly distinguishes this search tool from the account, recipient, and spending siblings.

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?

The description implies its role as a broad federal award search and links downstream to usaspending_get_award, but it never explicitly tells an agent when to prefer this tool over usaspending_search_federal_accounts, usaspending_search_recipients, or the spending analysis tools. The schema hints at autocomplete helpers, but the main description does not state exclusions or alternatives.

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.