Skip to main content
Glama

Get a notice's opportunity brief

opportunity_brief
Read-onlyIdempotent

One notice (or expiring contract) as its SpendQuery brief, no AI: the notice's facts and deadline, the contract it likely follows and how sure the match is, the incumbent and its money at the agency, other contracts it may follow, who else wins this work at the agency (with set-aside eligibility from their own SAM.gov registrations and how likely each is to bid, read from award history only), the contracting office (active contracts, how often its competed contracts drew one offer, how it usually buys), what similar work was awarded for (award values with options, not bids; prepared by a job, so "pending" the first time: ask again in a few minutes), the competitors' GSA ceiling rates and the agency's IT budget. For the decision card, the timeline of the buy and file changes: get_notice.

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": {
      "notice_id": "<notice_id>"
    },
    "name": "opportunity_brief"
  }
}

Input Schema

NameRequiredDescriptionDefault
notice_idYesA SAM.gov notice id (the 32-character hex id in sam.gov/opp/<id>/view, or from search_notices), or an expiring contract's award key from recompetes (e.g. "CONT_AWD_N0010426FB406_9700_N0010426GB401_9700").

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/5.0
Behavior5/5

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

Annotations already cover read-only/idempotent/closed-world, but the description adds the non-obvious operational trait that the brief is 'prepared by a job, so "pending" the first time: ask again in a few minutes' — critical for an agent to avoid treating an empty result as missing data. It also discloses data provenance and limits: 'award history only,' set-asides from 'their own SAM.gov registrations,' and 'award values with options, not bids.'

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Content is front-loaded correctly and every clause carries real information, but the whole definition is a single run-on sentence with deeply nested parentheses, making it hard to scan. It would be stronger as a lead sentence plus a short list of brief components.

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?

Given a single fully-documented parameter and an existing output schema, the description goes well beyond what is required, covering async generation, data provenance, and the sibling split. The enumeration of return contents is partly redundant with the output schema, but nothing an agent needs to call it 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 coverage is 100% and the notice_id field already documents both the 32-char SAM.gov hex id and the expiring-contract award key with an example. The description only echoes the dual-input flexibility with '(or expiring contract)', adding little beyond the schema.

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?

Names a specific verb and resource ('One notice ... as its SpendQuery brief') and enumerates the concrete contents — deadline, likely predecessor contract with match confidence, incumbent, set-aside eligibility, office stats, comparable award values, ceiling rates. It also explicitly demarcates the sibling at the end: 'For the decision card, the timeline of the buy and file changes: get_notice.'

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?

Gives an explicit redirect to get_notice for the decision card and timeline, and tells the agent to retry when the brief comes back 'pending' the first time. It does not cover when a brief is unnecessary versus cheaper siblings like search_notices or award_prices, so the exclusion set is partial.

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