Skip to main content
Glama

Watch a company: its new awards, re-bids and notices

competitor_watch
Read-onlyIdempotent

What is new with one company (a competitor, a teaming partner, a prime), from the records, no AI: its new awards (base awards to it or a subsidiary in the last 45 days of loaded data, largest first; Defense publishes about 90 days late), its contracts ending within 12 months as incumbent (with the follow-on SAM.gov notice when one is posted: the re-bids to watch), and open SAM.gov notices in its main industries (its top NAICS codes by contract dollars in the last two fiscal years), newest first. On spendquery.com a signed-in user can follow the company and get these weekly by e-mail.

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": {
      "company": "<company>"
    },
    "name": "competitor_watch"
  }
}

Input Schema

NameRequiredDescriptionDefault
companyYesA company UEI (12 characters), name or ticker, e.g. "Leidos" or "YMZ1PCB5LEM9".

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already cover readOnly/idempotent/non-destructive, and the description goes well beyond them: it discloses the 45-day lookback on loaded data, the ~90-day Defense publication lag, the 12-month ending-contract horizon, that notices are keyed to top NAICS by contract dollars over the last two fiscal years, and the sort orders ('largest first', 'newest first'). It also notes the weekly e-mail follow feature tied to a signed-in account, which is behavior an agent cannot get from structured fields.

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 opening clause ('What is new with one company') is the right lead, and every clause carries substantive information about windows, sort orders, or data lag. It loses a point for being a single long run-on sentence with heavy nested parentheticals, which makes it harder to parse than a short bulleted or multi-sentence structure would.

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 and the description still summarizes what comes back in each of the three sections, so an agent knows what to expect before calling. Combined with the data-lag and window caveats, nothing material is missing for a one-parameter read-only tool.

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 single parameter already documents UEI (12 characters), name, or ticker formats, so the baseline is 3. The description adds meaning by naming the acceptable entity types (competitor, teaming partner, prime), clarifying the scope of the resolved entity.

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+resource with three concrete outputs enumerated: new awards in the last 45 days, incumbent contracts ending within 12 months with follow-on SAM.gov notices, and open notices in the company's top NAICS codes. This is clearly distinguishable from siblings like company_profile (static profile) and search_notices (open search), because it is scoped to one company's delta activity.

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 strong contextual framing for when to reach for it: watching a competitor, teaming partner, or prime, and it flags 'the re-bids to watch' as the intent behind the ending-contracts output. It stops short of explicitly naming an alternative sibling (e.g., recompetes for cross-company re-bid sweeps) or stating when-not to use it, so it earns 4 rather than 5.

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