Skip to main content
Glama

Fcc

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Census Area

census_area
Read-onlyIdempotent

Resolve a US latitude/longitude (decimal degrees) to its full Census area record: block/county/state FIPS + names plus 2020 block population and FCC market-area codes (BEA, BTA, CMA, EAG, MEA, MTA, PEA, REA, RPC, VPC). Richer than census_block; use when you need population or FCC licensing market codes for a point.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
latYesLatitude in decimal degrees (e.g. 38.8976).
lonYesLongitude in decimal degrees (e.g. -77.0365).
censusYearNoCensus vintage: "2020" (default) or "2010".

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "lat": 38.8976,
+    "lon": -77.0365
+  },
+  {
+    "censusYear": "2010",
+    "lat": 34.0522,
+    "lon": -118.2437
+  }
+]
  2. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already mark readOnly, idempotent, not destructive. Description adds that it resolves a point to a record with specific data, and mentions richness relative to census_block, which adds value without contradicting annotations.

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?

Two sentences, both substantive. No filler, clearly front-loaded with output detail and sibling comparison.

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?

With no output schema, description effectively lists return fields (FIPS, population, FCC codes). Could mention coordinate range for US or error handling, but covers essential inputs and outputs.

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

Parameters3/5

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

Schema description coverage is 100%, so description adds little beyond schema. It restates that lat/lon are in decimal degrees and censusYear has enum values, but no new meaning.

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 resolves US lat/lon to full Census area record, listing specific outputs (FIPS codes, population, FCC codes). It distinguishes from sibling 'census_block' by calling itself richer and specifying when to use it.

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 says 'use when you need population or FCC licensing market codes for a point' and contrasts with the simpler census_block, providing clear context for when to choose this tool over an alternative.

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

All Fcc toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources