Skip to main content
Glama

Assess an opportunity

assess_opportunity
Read-onlyIdempotent

Use this when the user asks if one opportunity is a good fit for them, whether to bid, or wants a bid brief: days left, set-aside match, similar past awards at the same agency, the firms that usually win such work and the usual award value.

Pass the id from a search_contracts or search_grants result (not an award id), and optionally my_naics (up to 10 codes) and my_set_aside to check the fit. Similar awards come from MatchAwards' award records for the same NAICS at the same agency, or at all agencies when that agency has none (basis says which); sample gives the dates covered and whether every matching record was read, so state that span rather than a longer one. Award records may be incomplete, so say so; ai text is AI-generated, so label it. Never call a firm the incumbent: these are firms that won similar work. Example: id="117412688283576625".

Print url, sam_url and each award's url and source_url as markdown links.

Do not use for searching (search_contracts, search_grants), for finding partners (find_teaming_partners) or for job postings.

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": {
      "id": "<id>"
    },
    "name": "assess_opportunity"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesAn opportunity's id from a search result (the tool says which searches); not an award id (search_awards, get_company).
my_naicsNoUp to 10 six-digit NAICS codes, comma-separated, e.g. '236220' or '541511,541512'. A record matches on its own codes (matched_naics says which). Unknown codes are ignored.
my_set_asideNoThe user's set-aside code, e.g. 'SBA' or 'SDVOSBC', to compare with the opportunity's.

Output Schema

NameRequiredDescriptionDefault
aiNoAI-generated notes on this opportunity, or null. Label them as AI-generated when you show or quote them.
noteNo
as_ofNo
basisNo'same NAICS and agency', 'same NAICS, all agencies', or null (no NAICS).
sampleYes
warningNoSet when the award lookup was cut short; the figures cover what was read.
naics_matchNoWhether the opportunity's NAICS is one of my_naics; null when my_naics was not given.
opportunityYes
coverage_noteNo
similar_awardsYesThe 5 newest similar awards.
set_aside_matchNoWhether the opportunity is set aside for my_set_aside; null when it was not given. An opportunity without a set-aside is open to all firms.
typical_winnersYesUp to 5 firms that won similar work, most awards first, then largest total.
award_value_rangeNoQuartiles of the similar awards' amounts (USD); null with fewer than 3 amounts.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / id / description
      Previous value: -"The id field of a search result."New value: +"An opportunity's id from a search result (the tool says which searches); not an award id (search_awards, get_company)."
    • 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
Behavior5/5

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

Annotations already cover the read-only/idempotent safety profile, and the description adds substantial context beyond them: the data provenance for similar awards (MatchAwards records, same NAICS at same agency, falling back to all agencies with 'basis' saying which), the 'sample' field's coverage semantics, and the warning that award records may be incomplete. It also flags AI-generated text for labeling and warns against calling firms 'incumbents' — real behavioral constraints an agent would otherwise get wrong.

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-loaded with the triggering scenario, then parameter guidance, then output-caveat rules, then exclusions — a sensible order. Some sentences are response-formatting directives (markdown links, 'state that span') rather than tool description, which slightly dilutes focus, but nothing is redundant.

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?

An output schema exists, so return values need not be enumerated, and the description instead covers what the agent must do with them: disclose the sample span, flag incomplete records, label AI text, and avoid mislabeling winning firms as incumbents. Combined with the fully covered parameter schema and annotations, nothing needed to call or report this tool correctly is missing.

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 three parameters, including the id provenance and the 10-code NAICS limit. The description restates the id source and the optional my_naics/my_set_aside purpose ('to check the fit') but adds no format or syntax detail beyond the schema, so the baseline 3 applies.

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 states a specific verb and resource (assess one opportunity's fit) and enumerates exactly what the assessment returns: days left, set-aside match, similar past awards at the same agency, usual winners and award value. It also explicitly distinguishes itself from get_opportunity-style retrieval and from the search tools, so an agent can route correctly 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?

Opens with the triggering user intents ('asks if one opportunity is a good fit', 'whether to bid', 'wants a bid brief') and closes with explicit exclusions naming the right alternatives for searching, partner-finding, and job postings. Both the when and the when-not are stated, plus the prerequisite that the id comes from a search_contracts or search_grants result rather than an award id.

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.