Skip to main content
Glama

usaspending-mcp-server

Spending by Category

usaspending_spending_by_category
Read-onlyIdempotent

Aggregate federal spending grouped by a specific dimension: NAICS industry code, PSC product/service code, awarding agency, funding agency, CFDA assistance program, or recipient. Returns top items with obligation amounts — useful for trend and breakdown analysis. Filter by keyword, award type, agency, recipient, NAICS code, Assistance Listing, PSC, DEF code, or date range. Chain NAICS, PSC, and CFDA codes back into these filters, into usaspending_search_awards filters, or into usaspending_autocomplete_filters lookups. recipient_duns rows carry recipient_id, which opens the recipient profile in usaspending_get_recipient, and uei.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNoPage number (1-based)
limitNoMaximum items to return (1–100)
filtersNoOptional filters to scope the aggregation
categoryYesBreakdown dimension: naics (industry), psc (product/service code), awarding_agency, awarding_subagency, funding_agency, funding_subagency, cfda (assistance programs), or recipient_duns (recipients)

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNoCurrent page returned
errorNoPresent when the call failed. Absent on success.
noticeNoNames a date bound that was filled in because only the other was supplied, and — when results are empty — names any Assistance Listing, PSC, or DEF codes sent and suggests how to broaden filters. Absent when neither applies.
resultsNoTop items in this category by obligation amount
categoryNoBreakdown dimension used
has_nextNoWhether there are more pages
totalCountNoTotal number of items in this category (when available)
page_metadataNoPagination metadata
applied_keywordsNoKeyword filters applied (comma-separated)
applied_def_codesNoDEF codes sent, uppercased (comma-separated)
applied_psc_codesNoPSC codes sent, uppercased (comma-separated)
applied_agency_nameNoAwarding agency name filter applied
applied_naics_codesNoNAICS code filters applied (comma-separated)
applied_time_period_endNoEnd date sent (YYYY-MM-DD), including a filled-in end
applied_time_period_startNoStart date sent (YYYY-MM-DD), including a filled-in start
applied_assistance_listingsNoAssistance Listing numbers sent (comma-separated)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed16 schema fields changed
    • changedInput schema / properties / category / description
      Previous value: -"Breakdown dimension: naics (industry), psc (product/service code), awarding_agency, awarding_subagency, funding_agency, funding_subagency, cfda (assistance programs), recipient_duns, or recipient_parent_duns"New value: +"Breakdown dimension: naics (industry), psc (product/service code), awarding_agency, awarding_subagency, funding_agency, funding_subagency, cfda (assistance programs), or recipient_duns (recipients)"
    • changedInput schema / properties / category / enum
      Previous value: -[
      -  "naics",
      -  "psc",
      -  "awarding_agency",
      -  "awarding_subagency",
      -  "funding_agency",
      -  "funding_subagency",
      -  "cfda",
      -  "recipient_duns",
      -  "recipient_parent_duns"
      -]New value: +[
      +  "naics",
      +  "psc",
      +  "awarding_agency",
      +  "awarding_subagency",
      +  "funding_agency",
      +  "funding_subagency",
      +  "cfda",
      +  "recipient_duns"
      +]
    • addedInput schema / properties / filters / additionalProperties
      Added value: +false
    • changedInput schema / properties / filters / properties / agency_name / description
      Previous value: -"Awarding agency name filter"New value: +"Awarding agency name filter, top-tier only (e.g., \"Department of Defense\") — the toptier_name from usaspending_autocomplete_filters type=awarding_agency; a sub-agency name matches nothing"
    • addedInput schema / properties / filters / properties / assistance_listings
      Added value: +{
      +  "description": "Filter by Assistance Listing (CFDA) program numbers, e.g. [\"15.507\"]: 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 matching award's primary listing can differ from the one requested, and amounts cover the whole award, not that listing's share. Only assistance awards (grants, direct payments, loans, other assistance) carry listings, so a call whose award types are all contracts or IDVs — including a contract default — is rejected as assistance_listings_type_mismatch. Use usaspending_autocomplete_filters type=cfda to look up numbers.",
      +  "items": {
      +    "description": "Assistance Listing number, e.g. 15.507",
      +    "pattern": "^\\d{2}\\.[0-9A-Z]{3}$",
      +    "type": "string"
      +  },
      +  "type": "array"
      +}
    • addedInput schema / properties / filters / properties / def_codes
      Added value: +{
      +  "description": "Filter by Disaster Emergency Fund Codes (DEF), e.g. [\"Z\"], or [\"L\", \"M\", \"N\", \"O\", \"P\"] for COVID-19: 1–3 letters or digits, sent uppercased — the codes usaspending_disaster_spending takes and usaspending_get_agency lists. Matches awards of any type funded under any of these codes. Amounts cover the whole matching award, not the share funded by the code, and DEF-filtered totals can be negative. An unknown code is rejected with the list of codes USAspending accepts.",
      +  "items": {
      +    "description": "Disaster Emergency Fund Code, e.g. Z or L",
      +    "pattern": "^[0-9A-Za-z]{1,3}$",
      +    "type": "string"
      +  },
      +  "type": "array"
      +}
    • addedInput schema / properties / filters / properties / psc_codes
      Added value: +{
      +  "description": "Filter by Product and Service Codes (PSC), e.g. [\"Y1NE\"]: 1–4 letters or digits, sent uppercased. A shorter code covers every code under it (\"Y1\" covers \"Y1NE\"); several values match any of them. Only contracts and IDVs carry a PSC, so a call whose award types are all assistance types is rejected as psc_codes_type_mismatch, and pairing psc_codes with assistance_listings matches nothing, since no award carries both. Use usaspending_autocomplete_filters type=psc to look up codes.",
      +  "items": {
      +    "description": "Product and Service Code or prefix, e.g. Y1NE or Y1",
      +    "pattern": "^[0-9A-Za-z]{1,4}$",
      +    "type": "string"
      +  },
      +  "type": "array"
      +}
    • addedOutput schema / properties / applied_assistance_listings
      Added value: +{
      +  "description": "Assistance Listing numbers sent (comma-separated)",
      +  "type": "string"
      +}
    • addedOutput schema / properties / applied_def_codes
      Added value: +{
      +  "description": "DEF codes sent, uppercased (comma-separated)",
      +  "type": "string"
      +}
    • addedOutput schema / properties / applied_psc_codes
      Added value: +{
      +  "description": "PSC codes sent, uppercased (comma-separated)",
      +  "type": "string"
      +}
    • 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. `date_range_inverted`: Both filters.time_period_start and filters.time_period_end were supplied and the start falls after the end. `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. `date_range_inverted`: Both filters.time_period_start and filters.time_period_end were supplied and the start falls after the end. `date_before_earliest`: The resolved start date precedes the 2007-10-01 earliest date this endpoint can search. `assistance_listings_type_mismatch`: filters.assistance_listings was given while every code in filters.award_type_codes is a contract or IDV code. `psc_codes_type_mismatch`: filters.psc_codes was given while every code in filters.award_type_codes is an assistance code. 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",
      -  "date_range_inverted",
      -  "date_before_earliest"
      -]New value: +[
      +  "api_unavailable",
      +  "api_timeout",
      +  "date_range_inverted",
      +  "date_before_earliest",
      +  "assistance_listings_type_mismatch",
      +  "psc_codes_type_mismatch"
      +]
    • changedOutput schema / properties / notice / description
      Previous value: -"Names a date bound that was filled in because only the other was supplied, and suggests how to broaden filters when results are empty. Absent when neither applies."New value: +"Names a date bound that was filled in because only the other was supplied, and — when results are empty — names any Assistance Listing, PSC, or DEF codes sent and suggests how to broaden filters. Absent when neither applies."
    • changedOutput schema / properties / results / items / properties / code / description
      Previous value: -"Code value (NAICS, PSC, CFDA number, etc.)"New value: +"Code value (NAICS, PSC, CFDA number, recipient DUNS, etc.)"
    • addedOutput schema / properties / results / items / properties / recipient_id
      Added value: +{
      +  "description": "Recipient hash ID (recipient_duns rows) — pass to usaspending_get_recipient for the profile. Absent when upstream has none.",
      +  "type": "string"
      +}
    • addedOutput schema / properties / results / items / properties / uei
      Added value: +{
      +  "description": "Recipient Unique Entity Identifier (recipient_duns rows). Absent when upstream has none.",
      +  "type": "string"
      +}
  2. Changed11 schema fields changed
    • 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)"New value: +"End date (YYYY-MM-DD). Given alone, the window 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)"New value: +"Start date (YYYY-MM-DD), 2007-10-01 or later. Given alone, the window runs through today (UTC)."
    • removedInput schema / properties / filters / properties / time_period_start / type
      Removed value: -"string"
    • changedOutput schema / properties / applied_time_period_end / description
      Previous value: -"End date filter applied (YYYY-MM-DD)"New value: +"End date 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 date 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. 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. `date_range_inverted`: Both filters.time_period_start and filters.time_period_end were supplied and the start falls after the end. `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."
    • changedOutput schema / properties / error / properties / data / properties / reason / examples
      Previous value: -[
      -  "api_unavailable",
      -  "api_timeout"
      -]New value: +[
      +  "api_unavailable",
      +  "api_timeout",
      +  "date_range_inverted",
      +  "date_before_earliest"
      +]
    • changedOutput schema / properties / notice / description
      Previous value: -"Recovery hint when results are empty — suggests how to broaden filters. Absent when results are present."New value: +"Names a date bound that was filled in because only the other was supplied, and suggests how to broaden filters when results are empty. Absent when neither applies."
  3. 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": [
      +      "category",
      +      "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. Other values are possible when a failure originates below the handler.",
      +          "examples": [
      +            "api_unavailable",
      +            "api_timeout"
      +          ],
      +          "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: -[
      -  "category",
      -  "results",
      -  "page_metadata",
      -  "page",
      -  "has_next"
      -]
  4. Changed2 schema fields changed
    • removedOutput schema / properties / total
      Removed value: -{
      -  "description": "Total number of items in this category (when available)",
      -  "type": "number"
      -}
    • addedOutput schema / properties / totalCount
      Added value: +{
      +  "description": "Total number of items in this category (when available)",
      +  "type": "number"
      +}
  5. Changed5 schema fields changed
    • addedOutput schema / properties / applied_agency_name
      Added value: +{
      +  "description": "Awarding agency name filter applied",
      +  "type": "string"
      +}
    • addedOutput schema / properties / applied_keywords
      Added value: +{
      +  "description": "Keyword filters applied (comma-separated)",
      +  "type": "string"
      +}
    • addedOutput schema / properties / applied_naics_codes
      Added value: +{
      +  "description": "NAICS code filters 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"
      +}
  6. Changed6 schema fields changed
    • addedOutput schema / properties / has_next
      Added value: +{
      +  "description": "Whether there are more pages",
      +  "type": "boolean"
      +}
    • removedOutput schema / properties / message
      Removed value: -{
      -  "description": "Recovery hint when results are empty — suggests how to broaden filters. Absent when results are present.",
      -  "type": "string"
      -}
    • addedOutput schema / properties / notice
      Added value: +{
      +  "description": "Recovery hint when results are empty — suggests how to broaden filters. Absent when results are present.",
      +  "type": "string"
      +}
    • addedOutput schema / properties / page
      Added value: +{
      +  "description": "Current page returned",
      +  "type": "number"
      +}
    • addedOutput schema / properties / total
      Added value: +{
      +  "description": "Total number of items in this category (when available)",
      +  "type": "number"
      +}
    • changedOutput schema / required
      Previous value: -[
      -  "category",
      -  "results",
      -  "page_metadata"
      -]New value: +[
      +  "category",
      +  "results",
      +  "page_metadata",
      +  "page",
      +  "has_next"
      +]
  7. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/openWorld, so the bar is lower, and the description adds non-obvious behavior: results are "top items with obligation amounts" and recipient_duns rows carry recipient_id and uei. It does not mention pagination over the result set, but the schema covers page/limit defaults.

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 purpose, then return shape, then filters, then chaining — a logical order with no filler sentences. The filter enumeration partially duplicates the schema, costing a little efficiency, but every sentence is informative.

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

Completeness4/5

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

With an output schema present the description needn't explain return values, and it correctly focuses on dimension choice, filtering, and cross-tool chaining. Only a note on result pagination/ordering is missing, which is a minor gap given the page/limit parameters.

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 the schema already carries field-level semantics; the description only restates the filterable categories and adds a cross-tool chaining note. No syntax or format detail beyond what the schema provides, so baseline 3 is correct.

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?

Starts with a specific verb+resource (aggregate federal spending) and enumerates the grouping dimensions, matching the category enum. It is clearly distinguishable from sibling aggregators like usaspending_spending_by_geography and usaspending_spending_over_time.

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

Usage Guidelines4/5

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

States the analytical use case ("useful for trend and breakdown analysis") and gives explicit routing guidance: chain NAICS/PSC/CFDA codes into these filters, into usaspending_search_awards, or into usaspending_autocomplete_filters, and recipient_duns output into usaspending_get_recipient. It does not state when NOT to use it versus the other spending_* aggregators, so it stops short of 5.

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.