Skip to main content
Glama

Compare internet

compare_internet
Read-onlyIdempotent

Sourced plan comparisons for a Canadian province, plus Starlink. Optional region: annapolis-valley (alias valley) or national (alias canada). A province without a local table returns only providers whose published pages list service there, plus Starlink. Read only.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "province": "<province>"
    },
    "name": "compare_internet"
  }
}

Input Schema

NameRequiredDescriptionDefault
regionNoAllowed: annapolis-valley, valley, national, canada. valley is an alias for annapolis-valley. canada is an alias for national. Omit for the province default.
providerNo
provinceYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / region / description
      Added value: +"Allowed: annapolis-valley, valley, national, canada. valley is an alias for annapolis-valley. canada is an alias for national. Omit for the province default."
  2. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare read-only, idempotent, closed-world, non-destructive behavior, and the description mostly repeats 'Read only.' The fallback rule for provinces without a local table is useful behavioral context, but it doesn't explain result structure, provider filtering, or other operational details.

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?

Three short sentences are front-loaded with the purpose and scope, and no sentence is bloated. The concluding 'Read only' is redundant with annotations and alias details duplicate the schema, but overall it is tight.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a three-parameter comparison tool with no output schema, the description establishes purpose and region fallback behavior but leaves the provider parameter and the shape of comparison results unaddressed. An agent can make a basic call, but not with full confidence about filtering semantics.

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

Parameters2/5

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

Schema coverage is only 33%, and the description compensates only for region, repeating alias rules already present in the schema. The provider parameter is never explained, and province is only implied by geographic wording, so the description adds little parameter meaning beyond structured fields.

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 (sourced plan comparisons) and geographic scope (Canadian province plus Starlink), so the tool's purpose is immediately clear. It does not explicitly distinguish this from related offer tools such as starlink_offer or local_offer, so it falls short of full sibling differentiation.

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?

It describes optional region choices and a fallback rule for provinces without a local table, which implies when the tool is appropriate. However, it never states when to choose this over alternatives or any exclusions, leaving the agent to infer usage.

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