Skip to main content
Glama

fcc-broadband-mcp-server

by io.github.cyanheads

Search Broadband Availability

fcc_search_availability
Read-onlyIdempotent

Queries broadband providers and advertised speeds at a census block from FCC Form 477 data (as of June 2021). Answers "which ISPs serve this location and what speeds do they offer?" — the core tool for address-level broadband lookup. Requires a 15-digit census block FIPS code; use fcc_geocode_block to convert coordinates first. Data reflects ISP-reported availability at the block level, which may overstate actual coverage for some addresses.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
consumerNoFilter to consumer service (true) or business service (false). Omit to return both consumer and business offerings.
block_fipsYes15-digit census block FIPS code on 2010 census boundaries, the vintage this Form 477 dataset is keyed by (e.g., "530330081002024"). Obtain from fcc_geocode_block using address coordinates — a 2020-vintage block ID matches no deployment row.
tech_filterNoTechnology codes to filter, from the complete Form 477 taxonomy: 0=All other, 10=Asymmetric xDSL, 11=ADSL2, 12=VDSL, 20=Symmetric xDSL, 30=Other copper wireline, 40=Cable modem, 41=Cable modem DOCSIS 1/1.1/2.0, 42=Cable modem DOCSIS 3.0, 43=Cable modem DOCSIS 3.1, 50=Fiber to the end user, 60=Satellite, 70=Terrestrial fixed wireless, 90=Electric power line. Omit to return all technologies.
min_speed_downNoMinimum advertised download speed in Mbps to include in results. Omit to return all providers regardless of speed.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
errorNoPresent when the call failed. Absent on success.
noticeNoRecovery hint when no providers are found — suggests how to broaden the query. Absent on successful results.
blockFipsNoThe queried census block FIPS code.
providersNoISP offerings reported for this census block.
dataVintageNoData vintage — all Form 477 data on FCC Open Data is as of June 2021. For newer BDC data, use fcc_list_downloads.
appliedFiltersNoFilters applied to this query.
totalProvidersNoTotal number of distinct holding companies offering service at this block.

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already cover read-only and idempotent behavior, so the description adds value by disclosing the data source vintage (June 2021), the requirement for 2010 census boundaries, and the caveat that ISP-reported availability may overstate actual coverage. This goes beyond the structured annotations with meaningful 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 a tight two-sentence summary that front-loads the core purpose, then adds the essential prerequisite and a caveat. Every sentence carries functional value with no filler.

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 tool's moderate complexity and the presence of a full output schema and thorough parameter descriptions, the overview covers purpose, usage, and data quality. It could mention potential empty results or error handling, but these are minor gaps; it's nearly complete for an agent to call correctly.

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?

With 100% schema coverage, the baseline is 3. The description adds a practical hint on obtaining the block_fips parameter (via fcc_geocode_block) and warns about vintage mismatches, which is useful beyond the schema. It doesn't elaborate on other parameters, so a 4 is warranted for the extra guidance.

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 states a specific verb ('queries') and resource ('broadband providers and advertised speeds at a census block'), and distinguishes itself as 'the core tool for address-level broadband lookup.' It clearly differentiates from siblings like fcc_compare_areas or fcc_get_provider by focusing on the block-level query scope.

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?

It explicitly instructs to 'use fcc_geocode_block to convert coordinates first,' providing a clear prerequisite. It also clarifies the data vintage and warns about potential overstatement. However, it does not explicitly list when not to use this tool versus alternatives like fcc_search_providers, so it lacks a full 'when-not' statement.

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

All fcc-broadband-mcp-server toolsInspect
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 resource and action: geocoding, availability lookup, provider search, provider details, coverage summaries, area comparisons, underserved analysis, data version listing, and file downloads. No two tools have overlapping purposes.

Naming Consistency5/5

All tools follow the `fcc_` prefix plus a clear verb_noun pattern (e.g., `fcc_geocode_block`, `fcc_search_availability`, `fcc_list_downloads`). Naming is consistent snake_case with a predictable structure.

Tool Count5/5

9 tools is well-scoped for a domain-specific data server. Each tool earns its place, covering the core workflow of geocoding, availability, provider lookup, coverage analysis, and data file access without redundancy.

Completeness4/5

The tool set covers the essential lifecycle: geocode → search availability, search providers → get provider, coverage summaries, comparisons, and data file discovery. Minor gaps exist (e.g., no direct address search, but geocoding prerequisites handle it), but the surface is comprehensive for FCC broadband analysis.

Resources