Skip to main content
Glama

Count the small businesses that can do a kind of work

rule_of_two
Read-onlyIdempotent

Rule of Two evidence (FAR 19.502-2: set an acquisition aside when at least two responsible small businesses can be expected to offer): the small firms, or the 8(a), HUBZone, SDVOSB or WOSB firms, that the government recorded as small on contract actions in an industry over the last three fiscal years, at the agency and in the state when given, and that are still registered in SAM.gov. Returns the count for each scope (here, the agency anywhere, government-wide), the firms with their awards, how the work has been bought (share to small businesses and through set-asides, by year), the registered pool, the size standard and text, the pack ready to send. It counts the record; the contracting officer decides.

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": "rule_of_two"
  }
}

Input Schema

NameRequiredDescriptionDefault
naicsYesThe industry: a NAICS code or words, e.g. "561720" or "janitorial".
stateNoWhere the work is performed, e.g. "VA" or "Virginia".
agencyNoThe buying agency, bureau or office, e.g. "VA", "Army".
programNoWhich firms to count: "small" (default), "8a", "hubzone", "sdvosb" or "wosb".small

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already establish readOnly, idempotent, non-open-world behavior, so the safety profile is covered. The description adds real context beyond that: the three-fiscal-year lookback, the SAM.gov registration filter, and the multi-scope return (counts per scope, firm-level awards, set-aside share by year, registered pool, size standard). The closing 'counts the record; the contracting officer decides' is a useful limitation caveat.

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 is embedded inside a long parenthetical FAR citation, so the front-loading is weak; an agent must parse the whole opening clause to reach the verb. The subsequent sentences are efficient but the overall block is dense and reads like a single run-on unit. Nothing is outright wasted, but readability suffers.

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?

With an output schema present and annotations covering safety, the description supplies the remaining needed context: data source, time window, registration filter, scope semantics, and the decision boundary. An agent could call it correctly from this definition. Minor gaps like result-size expectations or behavior when a NAICS/state combination yields no firms are unaddressed.

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 all four parameters are already documented, and the description largely restates those meanings ('at the agency and in the state when given'). It does spell out the `program` options in prose (8(a), HUBZone, SDVOSB, WOSB), matching the schema's enum-like default, but adds no new syntax or edge-case guidance. Baseline 3 is appropriate.

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?

The description names a specific resource and computation: counting small (or 8(a)/HUBZone/SDVOSB/WOSB) firms recorded on contract actions in an industry over the last three fiscal years that remain SAM-registered, framed as FAR 19.502-2 Rule of Two evidence. That is far more specific than the title. It does not explicitly name a sibling to contrast with (e.g. size_standard or naics_finder), so the sibling-differentiation bonus is not fully earned.

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?

The regulatory framing ('set an acquisition aside when at least two responsible small businesses can be expected to offer') makes the decision context concrete: this is the pre-set-aside evidence check for a NAICS in a place/agency. It also states a boundary on the tool's authority ('It counts the record; the contracting officer decides'). It stops short of naming when not to use it or which sibling to reach for instead.

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