Skip to main content
Glama

GroundTruth - Environmental Records

List FCC broadband availability for a location

broadband_availability
Read-onlyIdempotent

Fixed broadband availability for a US location from the FCC Broadband Data Collection (BDC), counted per 2020 Census block: each provider and technology the FCC data lists in the block, with advertised maximum download and upload tiers in Mbps and how many of the block's locations each covers (residential and business-only counts). FCC data as of 2025-12-31 (release D25_19oct2026). Wired and fixed wireless service comes first; satellite service is listed last, in its own section. Where a point is in no Census block with FCC data, counts are for the surrounding H3 cell. A block where the FCC records no locations (often a park, a plaza or a street) lists no providers; the building's own address finds the block it sits in. Speeds are advertised maximums reported by providers, not measured speeds. The FCC data has no street addresses, so it cannot confirm service at one house. Input is either a street address (geocoded by the US Census geocoder) or lat/lon coordinates.

Input Schema

NameRequiredDescriptionDefault
latNoLatitude (US)
lonNoLongitude (US; negative except Guam, NMI and the western Aleutians)
addressNoUS street address incl. city/state (alternative to lat/lon)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.8/5.0
Behavior5/5

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

The description adds massive behavioral context beyond the simple readOnly/idempotent annotations. It specifies the data nature (maximum advertised speeds, not measured), the data source age (2025-12-31), and the organizational structure of the results (Wired/Fixed Wireless before Satellite).

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?

The description is highly detailed, which is unavoidable given the complexity of the underlying FCC data, but it is well-structured. Each sentence contributes crucial, non-redundant information (data source, resolution, limitations) without unnecessary filler.

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?

The description is exceptionally complete for a complex, data-intensive external tool. It addresses potential user confusion regarding speeds (maximum vs. measured), resolution (census block vs. H3 cell), and data limitations (no service confirmation at single houses).

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?

Since schema coverage is 100%, the description does not need to explain individual parameters. However, it provides vital semantic context regarding input handling, specifying that the input can be a geocoded address or lat/lon, adding functional depth to the schema definition.

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 the tool's function (List FCC broadband availability) and specifies the resource (FCC Broadband Data Collection) and scope (US location census blocks). It distinguishes itself from sibling tools by focusing specifically on the broadband data availability.

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

Usage Guidelines5/5

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

While it does not explicitly state 'when to use this vs. siblings,' it provides comprehensive usage guidance by defining the operational boundaries and limitations of the data. It clarifies how address input is processed and when H3 cells are used for resolution.

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