Skip to main content
Glama

Get company award history

get_company
Read-onlyIdempotent

Use this when the user wants one firm's government award history and its UEI is known, e.g. from a search_awards row.

Returns the firm's name and other spellings, location (city, state, country), totals for contract and grant awards, first and last award dates, top NAICS codes and agencies, and its 10 most recent awards. No contact details. Award records may be incomplete, so say so. Example: uei="C3KXNLTAAY98".

Print each recent award's url and source_url as markdown links; an award id is not an opportunity id, so get_opportunity does not take it.

Do not use for finding firms by name or NAICS (search_awards) or for contact details (none are available).

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": {
      "uei": "<uei>"
    },
    "name": "get_company"
  }
}

Input Schema

NameRequiredDescriptionDefault
ueiYes12-character UEI, e.g. 'C3KXNLTAAY98'.

Output Schema

NameRequiredDescriptionDefault
ueiYes
dunsNo
nameNo
noteNo
as_ofNo
totalsNo
locationNo
top_naicsNoFrom contract awards only.
other_namesNoOther spellings in award records.
top_agenciesNo
coverage_noteNo
recent_awardsNoUp to 10, newest first.
last_award_dateNo
first_award_dateNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / $defs / AwardRow / properties / id / description
      Previous value: -"Award id; null when the award has no page on matchawards.com."New value: +"Award id; null when the award has no page on matchawards.com. Not an opportunity id: get_opportunity does not take it."
  2. Added

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), and the description still adds real value: what fields come back, the absence of contact details, the instruction to disclose incomplete award records, and the markdown-link rendering requirement for url/source_url. The only shortfall is that it does not mention result limits or pagination for anything beyond the 10 recent awards.

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?

It is front-loaded with the selection condition and organized into short, purposeful sentences; the output-formatting and caveat sentences each carry actionable content. Minor redundancy in repeating the UEI example that the schema already supplies.

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 single-parameter lookup with an output schema, the description covers everything an agent needs: selection criteria, alternatives, data-quality caveat, and output presentation rules. Return-field explanation is arguably redundant against the output schema but reinforces rather than omits.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% and the pattern/example are already documented, so the baseline is 3. The description goes slightly beyond by indicating provenance for the UEI (a search_awards row) and reinforcing the example format, which helps an agent source the value rather than invent one.

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 opening sentence names a specific verb (return) and resource (one firm's government award history) plus the key precondition (UEI known). It explicitly distinguishes itself from search_awards, which handles name/NAICS lookup, so an agent can route correctly without inspecting the 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 states when to use it (UEI known, e.g. from a search_awards row), when not to use it (finding firms by name or NAICS → search_awards; contact details → not available anywhere), and pre-empts a likely misuse by noting get_opportunity does not accept award ids. Alternatives and exclusions are both explicit.

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.