Skip to main content
Glama

Find teaming partners

find_partners
Read-onlyIdempotent

Not affiliated with the U.S. government, GSA, or SAM.gov. Not a U.S. government service. Find firms with a track record of teaming in a trade lane, based on historical subaward and prime-award activity. These are firms that might be worth a conversation, not recommendations. Inclusion is NOT a statement that a firm is seeking partners, has openings, or would be interested in any particular firm. WARNING: teaming with a large business can trigger affiliation rules that cost you your small business or set-aside eligibility (SDVOSB, 8(a), HUBZone). Size status shown is UNVERIFIED - check SAM.gov before relying on it. Exclusion screening is not established here; verify current status in SAM.gov. Present as information only; do not frame results as a partnership recommendation. Follow-ups within 30 minutes after a search ride free (up to 30 per search); otherwise one accepted call counts as one use.

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": {
      "naics": "<naics>"
    },
    "name": "find_partners"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum 25 records; minimum 1; default 10.
naicsYesNAICS code for the trade lane

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / limit / description
      Added value: +"Maximum 25 records; minimum 1; default 10."
  2. Changed1 schema field changed
    • addedInput schema / properties / naics / pattern
      Added value: +"^[0-9]{2,6}$"
  3. First observed

TDQS

A3.8/5.0
Behavior5/5

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

Annotations already declare read-only, idempotent, open-world, non-destructive, but the description adds substantial context beyond them: data provenance (historical subaward and prime-award activity), a data-quality warning that size status is UNVERIFIED and exclusion screening is not established, an affiliation-rule risk warning, and concrete quota behavior ('follow-ups within 30 minutes ride free, up to 30 per search; otherwise one accepted call counts as one use'). No contradiction with the read-only annotation.

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?

The core purpose sentence is buried behind three near-redundant legal disclaimers ('Not affiliated with the U.S. government, GSA, or SAM.gov. Not a U.S. government service.'), which hurts front-loading. Most remaining sentences do carry genuine compliance or billing information, so the length is defensible but the ordering is not.

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?

For a two-parameter read-only lookup with a fully documented schema and no output schema, the description covers purpose, data provenance, caveats, and quota behavior adequately. The one real gap is the absence of any statement distinguishing it from the near-identically named find_teaming_partners sibling.

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 both parameters are documented in the schema, including limit bounds and the NAICS pattern, so the schema carries the semantic load. The description only loosely reframes naics as 'trade lane,' adding nothing about format or granularity (2- vs 6-digit) beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource: 'Find firms with a track record of teaming in a trade lane,' and even names the underlying data basis (historical subaward and prime-award activity). It does not differentiate itself from the very similarly named sibling find_teaming_partners, so an agent must still guess between the two.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage guidance is present but oriented toward output framing rather than tool selection: 'present as information only; do not frame results as a partnership recommendation' and 'these are firms that might be worth a conversation, not recommendations.' There is no explicit statement of when to call this versus find_teaming_partners or other search tools.

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