Skip to main content
Glama

get_federal_contract_intelligence

Read-only

Use when researching a company federal revenue concentration, identifying government contract competitors, or assessing vendor dependency on federal business. Returns contract obligation data by vendor, agency, NAICS code, and fiscal year from USASpending. Example: Acme IT Services — $847M federal obligations FY2023, 67% from DoD, 3 agencies representing 89% of revenue — high concentration risk for supply chain or M&A due diligence. Source: USASpending.gov synced data. $0.02 USDC per call.

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": {
      "vendor_name": "<vendor_name>"
    },
    "name": "get_federal_contract_intelligence"
  }
}

Input Schema

NameRequiredDescriptionDefault
stateNoTwo-letter state code for place of performance (e.g. PA, IL).
naics_codeNo
agency_nameNo
fiscal_yearNo
vendor_nameYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true, and destructiveHint=false, so the safety profile is covered structurally. The description adds genuinely new behavioral facts — data source (USASpending.gov synced data) and a per-call cost of $0.02 USDC — which are valuable for an agent budgeting calls. It stops short of describing pagination, latency, or what happens when vendor_name matches multiple entities.

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 text is front-loaded with the 'Use when' triggers, followed by return shape, a worked example, source, and price. Every sentence carries information, though the Acme example runs long and could be trimmed without losing meaning.

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 no output schema, the description correctly supplies a sample return shape (obligation totals, agency mix, concentration percentage), which is exactly what an agent needs to interpret results. Cost and data provenance round it out. The only notable shortfall is the undocumented state parameter and unclear fiscal_year typing, which matter for correct invocation of a 5-parameter tool.

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 only 20% — just one of five parameters (state) is documented in the schema. The description partially compensates by naming four filter dimensions (vendor, agency, NAICS code, fiscal year) that map to vendor_name, agency_name, naics_code, and fiscal_year. It omits the state parameter entirely and says nothing about fiscal_year format or vendor_name matching behavior, so the gap is narrowed but not closed.

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?

The description gives a specific verb and resource — 'Returns contract obligation data by vendor, agency, NAICS code, and fiscal year from USASpending' — which is far more concrete than the name alone. It does not, however, differentiate itself from plausible siblings such as get_vendor_contract_intelligence or get_gpo_contract_benchmark, leaving the agent to infer boundaries from names.

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?

Three explicit 'use when' scenarios are stated: revenue concentration research, competitor identification, and vendor dependency assessment. This is clear context-setting with a concrete example (Acme IT Services, 67% DoD, concentration risk), but no exclusion criteria or named alternative tools are given.

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