Skip to main content
Glama

Check internet availability

check_availability
Read-onlyIdempotent

Internet availability and fiber context for a US address or area. Give one geography shape: a street address (for example '520 South Main Street, Goshen, Indiana 46526'), lat+lng, FCC location_id, 5-digit ZIP, city+state (for example Warsaw, IN), state, or a city alone for disambiguation candidates. Address answers are one FCC location; city/state/ZIP answers are explicitly area-level and never a guarantee at a door. Every answer states precision, grain, source, as_of, and a canonical live page.

Input Schema

NameRequiredDescriptionDefault
latNoLatitude (use with lng as an alternative to address)
lngNoLongitude (use with lat)
zipNo5-digit US ZIP, e.g. '46580'
cityNoUS city, e.g. 'Warsaw'. Pass state when known; city alone returns candidates.
stateNoTwo-letter USPS code or full state name, e.g. 'IN' or 'Indiana'
addressNoUS street address, e.g. '520 South Main Street, Goshen, Indiana 46526'
location_idNoFCC location id from a previous check (skips address resolution)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed12 schema fields changed
    • addedInput schema / anyOf
      Added value: +[
      +  {
      +    "required": [
      +      "location_id"
      +    ]
      +  },
      +  {
      +    "required": [
      +      "address"
      +    ]
      +  },
      +  {
      +    "required": [
      +      "lat",
      +      "lng"
      +    ]
      +  },
      +  {
      +    "required": [
      +      "zip"
      +    ]
      +  },
      +  {
      +    "required": [
      +      "city",
      +      "state"
      +    ]
      +  },
      +  {
      +    "required": [
      +      "state"
      +    ]
      +  },
      +  {
      +    "required": [
      +      "city"
      +    ]
      +  }
      +]
    • changedInput schema / properties / address / description
      Previous value: -"US street address, e.g. '520 South 5th Street, Goshen, Indiana'"New value: +"US street address, e.g. '520 South Main Street, Goshen, Indiana 46526'"
    • addedInput schema / properties / address / minLength
      Added value: +1
    • addedInput schema / properties / city
      Added value: +{
      +  "description": "US city, e.g. 'Warsaw'. Pass state when known; city alone returns candidates.",
      +  "minLength": 1,
      +  "type": "string"
      +}
    • 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 (use with lat)"
    • addedInput schema / properties / lng / maximum
      Added value: +180
    • addedInput schema / properties / lng / minimum
      Added value: +-180
    • addedInput schema / properties / location_id / minLength
      Added value: +1
    • addedInput schema / properties / state
      Added value: +{
      +  "description": "Two-letter USPS code or full state name, e.g. 'IN' or 'Indiana'",
      +  "minLength": 2,
      +  "type": "string"
      +}
    • addedInput schema / properties / zip
      Added value: +{
      +  "description": "5-digit US ZIP, e.g. '46580'",
      +  "pattern": "^[0-9]{5}$",
      +  "type": "string"
      +}
  2. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already cover safety (readOnlyHint, idempotentHint, openWorldHint=false), so the bar is lower, and the description still adds real behavior: address answers resolve to one FCC location while city/ZIP/state answers are explicitly area-level and 'never a guarantee at a door.' It does not mention auth, rate limits, or error handling, which keeps it below 5.

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 purpose and the required 'one geography shape' rule are front-loaded, and each following sentence adds distinct information (precision semantics, response metadata). The enumeration is dense but none of it is 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?

With no output schema, the description carries the burden of describing returns, and it does so by naming the fields every answer contains (precision, grain, source, as_of, canonical live page). What is missing is failure behavior — e.g. what happens with an unresolvable address or an out-of-coverage lat/lng.

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?

Schema coverage is 100%, so the baseline is 3, but the description adds meaning the schema does not: it tells the caller that location_id comes from a previous check (skips resolution), that city alone returns disambiguation candidates, and — most usefully — what precision/grain each input shape produces in the answer.

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?

States a specific resource and scope: internet availability and fiber context for a US address or area, with the accepted geography forms named. It is clear what the tool returns, but it never distinguishes itself from siblings such as location_intelligence or area_intelligence, which sound overlapping.

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?

The description gives strong input-selection guidance ('Give one geography shape', with seven enumerated forms and an example for each of address and city+state) and explains that city/state/ZIP are area-level. That is invocation guidance, not tool-selection guidance: there is no statement of when to prefer this over the sibling intelligence tools, or any exclusion.

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