FCC Broadband Map

get_broadband_summary_by_state

Get state-level broadband availability summary.

Returns aggregated broadband statistics for the state including provider
counts and technology deployment. Useful for BEAD program analysis to
identify states with significant unserved/underserved populations.

Args:
    state_fips: 2-digit state FIPS code (e.g. '53' for Washington, '11' for DC).
                Always a string, never an integer.
    speed_download: Minimum download speed threshold in Mbps (default 25).
    speed_upload: Minimum upload speed threshold in Mbps (default 3).
    as_of_date: BDC filing date in YYYY-MM-DD format (default 2024-06-30).

Input Schema

TableJSON Schema

Name	Required	Default
`as_of_date`	No	2024-06-30
`state_fips`	Yes
`speed_upload`	No
`speed_download`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

TDQS

A4.3/5.0

Behavior3/5

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

No annotations are provided, so the description carries the burden. It describes the tool as returning data and lists parameters, which implies a read-only operation. However, it does not explicitly state that no data is modified, nor does it cover error handling or authentication requirements. The description is adequate but not rich in behavioral context.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is concise: two lines of purpose and an args list. Every sentence earns its place, and the structure is front-loaded with the key action and outcome. No unnecessary words.

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?

Given the presence of an output schema (so return values are covered), 4 parameters, and sibling tools, the description covers the essential purpose and parameter semantics. It lacks guidance on error conditions or data availability, but for a summary data retrieval tool, it is reasonably complete.

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

Parameters5/5

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

Schema description coverage is 0%, but the description's 'Args' section adds substantial meaning: it explains state_fips format with examples, clarifies speed thresholds as 'minimum', and specifies the date format and default. This fully compensates for the schema's lack of descriptions.

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?

The description clearly states it returns a state-level broadband availability summary and mentions provider counts and technology deployment. It differentiates from siblings like get_broadband_summary_by_county and get_broadband_by_location by specifying state aggregation and a use case (BEAD program analysis).

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 description gives a clear context for use (BEAD program analysis) but does not explicitly exclude alternatives or provide when-not-to-use guidance. Sibling tools exist for county-level or location-level data, but the description does not direct the agent to those when finer granularity is needed.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All FCC Broadband Map tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.4/5.0

Disambiguation5/5

Each tool targets a distinct scope: location point, county, state, and providers in county. There is no overlap in purpose, and descriptions clearly differentiate them.

Naming Consistency5/5

All tools follow the pattern 'get_<object>_by_<scope>' (e.g., get_broadband_by_location, get_providers_by_county). The naming is consistent and predictable.

Tool Count5/5

With 4 tools, the server covers the essential query types for broadband data (location, county summary, state summary, provider list). The count is well-scoped without being excessive.

Completeness4/5

The set covers the main use cases for querying FCC broadband data. Minor gaps exist, such as no batch or multi-location query, but core CRUD-like operations are present for a read-only API.

Resources

Need Help?