Skip to main content
Glama

Check an SBA size standard

size_standard
Read-onlyIdempotent

SBA small business size standards (13 CFR 121.201, the eCFR table): a NAICS code, a code prefix (5415) or industry words -> receipts ($ millions) or employees, exceptions and footnotes, and the programs that use them. Each row also carries proposed: the standard SBA proposed on August 20, 2026 (91 FR 53741) for the code's 4- or 5-digit group, and whether it is higher, the same, or measured another way. The proposal is NOT in force: say so, and answer "am I small?" from today's standard. With receipts and/or employees, simulation says for each code whether a firm of that size is small today and would be under the proposal (newly_small, stays_small, stays_large).

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": {
      "query": "<query>"
    },
    "name": "size_standard"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYesA 6-digit NAICS code (e.g. "541511"), a code prefix (e.g. "5415") or industry words (e.g. "custom software").
receiptsNoThe firm's average annual receipts in dollars (last 5 fiscal years), to test it against today's and the proposed standard, e.g. 40000000.
employeesNoThe firm's average number of employees (last 24 months), for the same test, e.g. 180.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / employees
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "number"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "description": "The firm's average number of employees (last 24 months), for the same test, e.g. 180.",
      +  "title": "Employees"
      +}
    • addedInput schema / properties / receipts
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "number"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "description": "The firm's average annual receipts in dollars (last 5 fiscal years), to test it against today's and the proposed standard, e.g. 40000000.",
      +  "title": "Receipts"
      +}
  2. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "additionalProperties": true,
      +  "title": "size_standardDictOutput",
      +  "type": "object"
      +}
  3. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already mark the tool read-only, idempotent, and non-destructive; the description adds material behavior beyond that: the eCFR data source, the proposed-standard caveat that it is not in force, the fields in each row, and the simulation labels. It clearly prevents misuse of the proposal as current law.

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-loads the resource and query forms, then layers the proposal caveat and simulation behavior. It is dense but every sentence carries useful information; minor tightening is possible around the proposal citation.

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?

Given an existing output schema and annotations, the description covers the critical context: data source, query flexibility, proposed-vs-current distinction, and simulation output labels. Nothing essential for correct invocation is missing.

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%, so the baseline is 3, but the description adds meaning about how query forms (code, prefix, words) map to results and how optional receipts/employees trigger simulation against today's and proposed standards. It does not add syntax constraints or edge-case handling, but the parameter interaction is well explained.

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 exactly what is looked up (SBA size standards under 13 CFR 121.201) and what a query can be (NAICS code, prefix, industry words), plus what the result maps to. This is clearly distinct from code-search siblings because it returns size thresholds, exceptions, footnotes, and program applicability.

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?

Explains the primary use case of answering 'am I small?' from today's standard, and when to supply receipts/employees to get a simulation. It does not explicitly name when to choose a sibling such as naics_finder or search_codes, so it falls short of full when/when-not/alternatives guidance.

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