Skip to main content
Glama

Find teaming partners

find_teaming_partners
Read-onlyIdempotent

Use this when the user wants possible teaming partners, subcontractors or primes for one opportunity: firms that won similar awards in the same state or at the same agency.

Pass the id from a search_contracts or search_grants result (not an award id), and optionally role (sub, prime or any). Returns up to 10 firms from MatchAwards' award records (same NAICS in the opportunity's state, then at its agency, else anywhere; sample gives the dates covered and whether every matching record was read), ranked by how many similar awards they won, each with a why line; get_company(uei) shows the history of a firm with a uei. No contact details. Award records may be incomplete, so say so; ai_subcontracting is AI-generated, so label it. Never call a firm the incumbent. Example: id="117412688283576625".

Print the opportunity's url and sam_url as markdown links.

Do not use for searching awards in general (search_awards), for one firm's history (get_company) 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": "find_teaming_partners"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesAn opportunity's id from a search result (the tool says which searches); not an award id (search_awards, get_company).
roleNosub: the user looks for subcontractors (smaller typical awards first among equals); prime: for a prime to join (larger first); any (default).any

Output Schema

NameRequiredDescriptionDefault
noteNo
roleYes
as_ofNo
sampleYes
warningNoSet when the award lookup was cut short; the list covers what was read.
partnersYesUp to 10 firms that won similar work.
opportunityYes
coverage_noteNo
ai_subcontractingNoAI-generated notes on subcontracting angles for this opportunity, or null. Label them as AI-generated when you show them.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field 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)."
  2. Added

TDQS

A4.4/5.0
Behavior4/5

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

Beyond the readOnly/idempotent/non-destructive annotations, the description discloses the 10-firm cap, the state-then-agency-then-anywhere fallback order, the ranking basis, that no contact details are returned, and two data-quality caveats (incomplete award records, AI-generated ai_subcontracting) plus how to label them. The remaining gap is that it never says whether results are cached or how stale the award sample can be, but the disclosure is well above what the annotations carry.

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?

The purpose and routing are front-loaded, and the trailing 'do not use for' sentence is efficient. However, the middle paragraph crams ranking, coverage, attribution, forbidden phrasing and markdown-link printing into one dense block, mixing return-shape detail (already covered by the output schema) with required behavior.

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 two-parameter, read-only lookup with a full input schema, an output schema and complete annotations, nothing an agent needs in order to call it correctly is missing. The unusual operator instructions (don't call a firm the incumbent, label AI-generated content) are exactly the kind of thing only the description can supply.

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 schema already explains both id and role, including the enum ordering logic. The description adds only a concrete id example and names the two specific searches that produce valid ids, which is marginal added value over a fully documented 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?

The first sentence names a specific verb and resource ("possible teaming partners, subcontractors or primes for one opportunity") and immediately scopes it with the matching criterion (similar awards in the same state or agency). It is clearly distinguishable from siblings like search_awards, get_company and search_jobs, which are named as wrong-fit cases.

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 the triggering user intent, the prerequisite (id from a search_contracts or search_grants result, not an award id) and an explicit exclusion list with the correct alternatives for each case. An agent can route between this, search_awards, get_company and search_jobs without consulting other definitions.

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.