Skip to main content
Glama

Neighborhood (hex) intelligence

location_intelligence
Read-onlyIdempotent

Res-8 hex intelligence (~0.46 km cells) for any US coordinate: how many FCC locations, providers by technology, fiber density, competition and underserved status, and best available speeds in that immediate neighborhood. Give lat+lng (for example Goshen, IN: 41.5820, -85.8344), or an H3 res-8 hex_id directly.

Input Schema

NameRequiredDescriptionDefault
latNoLatitude, e.g. 41.5820 for Goshen, IN
lngNoLongitude, e.g. -85.8344 for Goshen, IN
hex_idNoH3 res-8 cell id (alternative to lat/lng)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed8 schema fields changed
    • addedInput schema / anyOf
      Added value: +[
      +  {
      +    "required": [
      +      "hex_id"
      +    ]
      +  },
      +  {
      +    "required": [
      +      "lat",
      +      "lng"
      +    ]
      +  }
      +]
    • addedInput schema / properties / hex_id / pattern
      Added value: +"^88[0-9a-fA-F]{8}[fF]{5}$"
    • changedInput schema / properties / lat / description
      Previous value: -"Latitude"New value: +"Latitude, e.g. 41.5820 for Goshen, IN"
    • addedInput schema / properties / lat / maximum
      Added value: +90
    • addedInput schema / properties / lat / minimum
      Added value: +-90
    • changedInput schema / properties / lng / description
      Previous value: -"Longitude"New value: +"Longitude, e.g. -85.8344 for Goshen, IN"
    • addedInput schema / properties / lng / maximum
      Added value: +180
    • addedInput schema / properties / lng / minimum
      Added value: +-180
  2. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true and openWorldHint=false, so safety and determinism are covered. The description adds genuinely new behavioral context: results are limited to US coordinates and are keyed to a fixed ~0.46 km resolution. It says nothing about response time, rate limits, or what happens when a hex has no carrier data, which is a meaningful gap for a data-lookup tool.

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?

Two sentences, front-loaded with the resolution and scope before the input options, with no filler. The mid-sentence list of returned metrics is dense but each item carries information about what the agent will receive.

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, the description sensibly enumerates the returned metrics, and the input contract is fully covered by the schema. It is nearly complete for a read-only lookup; the remaining shortfall is the absence of sibling routing guidance against area_intelligence and check_availability.

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 coverage is 100% and every parameter carries its own description and example, so the baseline is 3. The description restates the anyOf choice ('lat+lng ... or an H3 res-8 hex_id directly') and repeats the Goshen example already present in the schema, adding no new semantics such as when the hex_id path is preferable.

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 the resource precisely (res-8 H3 hex, ~0.46 km cells) and enumerates what it returns: FCC location counts, providers by technology, fiber density, competition/underserved status, and best available speeds. It is clearly a neighborhood-level lookup rather than an address-level or regional one, so it is distinguishable from siblings like area_intelligence and check_availability, though it never names them.

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

Usage Guidelines3/5

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

Usage context is implied by 'for any US coordinate' and the resolution note, telling an agent this is a small-area query. There is no explicit when-to-use or when-not-to-use guidance versus area_intelligence (broader area) or check_availability (specific address), so the agent must infer the routing decision.

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