Skip to main content
Glama

USAC Funding Data (E-Rate, Rural Health Care, Lifeline)

search_open_erate_rhc_bids

Open E-Rate Form 470 bids and Rural Health Care Form 461/465 postings from USAC Open Data.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "search_open_erate_rhc_bids"
  }
}

Input Schema

NameRequiredDescriptionDefault
statesNo
categoryNo
datasetsNo
maxItemsNo
fundingYearNo
postedWithinDaysNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.8/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden and discloses almost nothing behavioral: no mention of result ordering, the 250-item cap, whether filters combine with AND semantics, or what a result contains. The only added context is the upstream source (USAC Open Data), which does not tell an agent how the call behaves.

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?

A single front-loaded sentence with zero filler or repetition. The brevity is a virtue structurally, though it reflects under-specification rather than disciplined editing.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a six-parameter, zero-required search tool with no annotations and no output schema, the definition is thin: an agent knows the data domain but not how to scope results meaningfully or what comes back. The domain naming is accurate and sufficient to select the tool, but not to invoke it with well-chosen filters.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% across six parameters, so the description must compensate and largely does not. It does implicitly name the two dataset families matching the 'datasets' enum (form470, rhc) and hints that Form 470 is tied to a funding year, but states nothing about 'states', 'category' (C1/C2), 'postedWithinDays', or 'maxItems'.

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 the exact datasets covered — E-Rate Form 470 bids and Rural Health Care Form 461/465 postings — and attributes them to USAC Open Data, which clearly separates this from siblings like search_expiring_unclaimed_frns or search_school_c2_budgets. It reads as a noun phrase rather than stating a verb, but the tool name supplies the 'search' action and the resource is unambiguous.

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

Usage Guidelines2/5

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

There is no guidance on when to use this tool, when not to, or which sibling to prefer for adjacent queries. An agent must infer from the domain vocabulary alone that this is the E-Rate/RHC procurement search rather than a cross-program catalog search.

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