Skip to main content
Glama

Gov Contracts Search

gov_contracts_search
Read-onlyIdempotent

Search AWARDED US state & local government contracts, normalized across jurisdictions (keyless open data). Filter by vendor (winning supplier), keyword (contract title/description), awarding agency, and minimum dollar amount. Covers state and county contract registries, pass a jurisdiction key (see gov_contracts_jurisdictions) to target one, or omit it to search all covered jurisdictions at once. Returns each contract with its ID, vendor, title, agency, amount, and dates. This is STATE/LOCAL award data (for federal contracts use USAspending/SAM tools).

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "limit": 20,
      "vendor": "Microsoft",
      "keyword": "software",
      "min_amount": 50000,
      "jurisdiction": "tx"
    },
    "name": "gov_contracts_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax contracts per jurisdiction (default 20, max 100).
agencyNoAwarding agency/department to match (case-insensitive substring). Not all jurisdictions carry an agency field.
vendorNoWinning vendor/supplier name to match (case-insensitive substring), e.g. "Microsoft".
keywordNoMatch against contract title/description (case-insensitive substring), e.g. "software", "road".
min_amountNoOnly contracts whose value is at least this many dollars.
jurisdictionNoJurisdiction key to target (e.g. "tx", "wa", "king-county-wa"). Omit to search all covered jurisdictions. Use gov_contracts_jurisdictions to list keys.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
      +  {
      +    "jurisdiction": "tx",
      +    "keyword": "software",
      +    "limit": 20,
      +    "min_amount": 50000,
      +    "vendor": "Microsoft"
      +  },
      +  {
      +    "agency": "transportation",
      +    "keyword": "road construction",
      +    "limit": 50
      +  }
      +]
  2. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnly/openWorld/idempotent/non-destructive, so the safety profile is covered; the description adds that access is keyless open data, that records are normalized across jurisdictions, and what fields come back (ID, vendor, title, agency, amount, dates). It does not discuss pagination behavior or how per-jurisdiction limits aggregate when jurisdiction is omitted, which is the main remaining gap.

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?

Purpose is front-loaded in the first clause and the rest is dense, filter-by-filter detail with no filler. Minor redundancy between 'Covers state and county contract registries' and the following jurisdiction sentence, but nothing wasteful enough to obscure the call.

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 compensates by listing returned fields, and it covers scope, filters, and the jurisdiction-key workflow for a zero-required-parameter search tool. It falls short only on result aggregation semantics when multiple jurisdictions are searched at once, which an agent may need to interpret `limit` correctly.

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 documents all six parameters in detail, including the caveat that agency is not present in every jurisdiction. The description's mapping of vendor to 'winning supplier' and keyword to title/description largely restates that, adding little new syntax, default, or format guidance beyond what the schema provides.

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: 'Search AWARDED US state & local government contracts, normalized across jurisdictions.' It also explicitly bounds the domain against federal award data and names the sibling (gov_contracts_jurisdictions) needed for jurisdiction keys, so an agent can separate it from gov_spending_search 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 explicit routing: pass a `jurisdiction` key to target one registry, omit it to search all; use gov_contracts_jurisdictions to list keys; use USAspending/SAM for federal contracts. That is a when-to-use plus an explicit when-not-to-use with a named alternative.

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.