Skip to main content
Glama

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

search_school_c2_budgets

School and library E-Rate Category 2 (Wi-Fi, switches, cabling) budgets 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_school_c2_budgets"
  }
}

Input Schema

NameRequiredDescriptionDefault
sortByNo
statesNo
maxItemsNo
budgetCycleNo
applicantTypesNo
budgetVersionsNo
minAvailableUsdNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.7/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden and discloses almost nothing: no default sort order, no default result cap, no pagination or result-count behavior, and no note that all seven filters are optional and combine conjunctively. Only the underlying data source (USAC Open Data) is added context.

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 no wasted words and the resource defined up front. Its brevity is efficient rather than padded, though it comes at the cost of under-specification flagged elsewhere.

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

Completeness2/5

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

For a seven-parameter search tool with no annotations, no output schema, and no parameter documentation, the description is far too thin. An agent cannot tell what a call returns, how many records, in what order, or how the filters interact.

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 seven parameters, so the description must compensate and largely does not. 'School and library' loosely hints at applicantTypes and 'Category 2' at budgetCycle, but states, sortBy, maxItems, budgetVersions, and minAvailableUsd get no explanation of meaning, allowed values, or defaults.

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 — school and library E-Rate Category 2 budgets (Wi-Fi, switches, cabling) sourced from USAC Open Data — which an agent could distinguish from the sibling datasets about FRNs, Lifeline carriers, and RHC bids. It lacks an explicit operation verb (search/list/retrieve) and does not differentiate itself from siblings in prose, so it falls short of a 5.

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 when-to-use guidance, no mention of alternatives, and no stated preconditions or typical query patterns. The agent must infer from the tool name that this is a filtered search over budget records.

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