Commerce for Agents

Compare US Home Internet Providers

compare-broadband

Read-onlyIdempotent

Fixed home internet providers available at a US address, from the FCC National Broadband Map: fiber, cable, DSL, fixed wireless, satellite with max advertised download/upload speeds and a low-latency flag. Keywords: internet providers near me, broadband, ISP, fiber internet, cable internet, home internet comparison. Input: a US street address (preferred) or lat+lon. Optional filters minDownloadMbps and technology. The result has no prices; say so and do not invent prices.

Input Schema

TableJSON Schema

Name	Required	Description
`lat`	No	Latitude, if no address is given.
`lon`	No	Longitude, if no address is given.
`address`	No	US street address incl. city and state or ZIP.
`technology`	No	Only these technologies.
`minDownloadMbps`	No	Only providers advertising at least this download speed.

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedSep 26, 2026

removedInput schema / properties / context

Removed value: -{
-  "description": "Why are you calling this tool? Briefly describe the user's goal.",
-  "type": "string"
-}

removedInput schema / required
```
Removed value: -[
-  "context"
-]
```

First observedSep 26, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already cover read-only, idempotent, open-world, and non-destructive behavior. The description adds valuable behavioral context beyond that: the data source (FCC National Broadband Map), the result contents (max speeds and low-latency flag), and the explicit warning that the result has no prices and agents should say so. No contradictions with annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The core function is front-loaded and the sentences are serviceable, but the 'Keywords:' block is redundant SEO-style noise that does not help an agent. The description would be tighter without it.

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?

There is no output schema, so the description rightly explains what the result contains (speeds, low-latency flag, no prices). It covers input modes, filters, and data source. Minor gaps such as error behavior or result ordering exist, but an agent has enough to call and interpret it correctly.

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 baseline is 3. The description adds slight meaning by noting address is preferred over lat/lon and naming the two filters, but it does not explain parameter semantics beyond what the schema already provides.

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 function: returning fixed home internet providers at a US address using FCC National Broadband Map data, with technology types, speeds, and a low-latency flag. This clearly distinguishes it from siblings like compare-mobile-plans and compare-tariffs.

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?

Clear usage context is given: input a US street address (preferred) or lat+lon, with optional minDownloadMbps and technology filters. It also instructs agents not to invent prices. It does not explicitly list when not to use this tool versus a specific sibling, but the context is unambiguous.

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

All Commerce for Agents tools Inspect

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

Need Help?