Skip to main content
Glama

Federal Contracts by Company

GetGovernmentContracts
Read-only

Get federal government contract awards won by a specific public company: US federal awards (from USAspending.gov) or Government of Canada contracts (from its proactive publication of contracts over C$10,000). Shows the award (action) date, recipient named by the government, awarding agency or department, total value (US: obligated dollars plus unexercised ceiling; Canada: contract value including amendments, in Canadian dollars; never revenue received), outlays when reported, end date, and description. Coverage: US prime contract awards of $1M or more, and Canadian contracts reported from fiscal 2017-2018 (April 2017) whose vendor name exactly matches a company listed on a Canadian exchange, so sums understate government revenue. Use GetTopGovernmentContractors to rank companies market-wide.

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": {
      "ticker": "<ticker>"
    },
    "name": "GetGovernmentContracts"
  }
}

Input Schema

NameRequiredDescriptionDefault
agencyNoOptional case-insensitive substring filter on the awarding agency (e.g., 'Defense')
offsetNoNumber of matching awards to skip before returning rows (default: 0)
sortByNoSort order: 'amount' (largest total value first, default) or 'date' (most recent award first)amount
tickerYesStock ticker symbol (e.g., LMT, RTX, BA), or MIC:TICKER for a Canadian listing (e.g., XTSE:CAE)
countryNoAwarding government: US or CA. Defaults to the country of the listing the symbol names (CA for XTSE:CAE, US for a bare US ticker)
endDateNoEnd date in YYYY-MM-DD format (defaults to today)
startDateNoStart date in YYYY-MM-DD format, filtering on the award action date (defaults to 1 year ago)
maxResultsNoMaximum number of awards to return (default: 50)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / country
      Added value: +{
      +  "default": null,
      +  "description": "Awarding government: US or CA. Defaults to the country of the listing the symbol names (CA for XTSE:CAE, US for a bare US ticker)",
      +  "type": "string"
      +}
    • changedInput schema / properties / ticker / description
      Previous value: -"Stock ticker symbol (e.g., LMT, RTX, BA)"New value: +"Stock ticker symbol (e.g., LMT, RTX, BA), or MIC:TICKER for a Canadian listing (e.g., XTSE:CAE)"
  2. Changed1 schema field changed
    • addedInput schema / properties / offset
      Added value: +{
      +  "default": 0,
      +  "description": "Number of matching awards to skip before returning rows (default: 0)",
      +  "type": "integer"
      +}
  3. 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=true, destructiveHint=false, and openWorldHint=false, so safety is covered. Beyond that, the description discloses the upstream sources, the exact meaning of the value field ('US: obligated dollars plus unexercised ceiling; Canada: contract value including amendments... never revenue received'), and warns that sums understate government revenue — genuine context the annotations cannot carry. It stops short of describing pagination or ordering behavior despite having offset/maxResults/sortBy.

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?

The purpose is front-loaded in the first clause, then output fields, then coverage caveats, then the sibling pointer — a sensible ordering. It is dense but nearly every clause carries information; the parenthetical on Canada's amendment-inclusive value is long but earns its place.

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 8 parameters, no output schema, and no enum constraints, the description carries the burden well by enumerating the returned fields (action date, recipient, agency, total value, outlays, end date, description). It also pre-empts the most likely misinterpretation — treating award value as recognized revenue — which is critical for correct downstream use.

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 coverage is 100%, so every parameter including the MIC:TICKER convention, country defaulting, and date formats is already documented. The description reinforces the entity scope ('a specific public company') and the funding-source semantics but adds no new per-parameter syntax or constraints beyond what the schema states.

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+resource ('Get federal government contract awards won by a specific public company') and immediately delimits the two data domains (USAspending.gov vs. Government of Canada proactive publication). An agent can distinguish this from GetTopGovernmentContractors without opening either 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?

It explicitly routes the agent to the alternative ('Use GetTopGovernmentContractors to rank companies market-wide'), which is exactly the case where this per-company tool is the wrong choice. It also states the coverage boundaries ($1M+ US prime awards; Canadian contracts from April 2017 with an exact vendor-name match) that determine when results will be trustworthy.

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.