Skip to main content
Glama

Compare internet and mobile tariffs

telecom
Read-onlyIdempotent

Sourced price lists, in preparation. action: internet (home internet by country, technology, speed, price) or mobile (tariffs by operator, data, commitment).

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": {
      "action": "<action>"
    },
    "name": "telecom"
  }
}

Input Schema

NameRequiredDescriptionDefault
sortNoprice, speed, price_per_mbps, price_per_gb
limitNoMax rows
actionYesOperation to run; help {topic:"telecom"} lists each one's arguments
detailNocompact (default) or full
offsetNoRows to skip
countryNoCountry code, e.g. CZ
data_gbNoData in GB (mobile)
operatorNoOperator (mobile)
providerNoProvider (internet)
max_priceNoMax monthly price
technologyNoFTTH, FTTB, optical, xDSL, CATV, FWA (internet)
min_speed_mbpsNoMin speed in Mbps
commitment_monthsNoMax commitment in months

Output Schema

NameRequiredDescriptionDefault
moreNoHow to fetch the next page
limitNo
totalNoAll matches, not just this page
offsetNo
returnedNo
cross_border_noteNo
commission_disclosureNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • addedInput schema / properties / action / description
      Added value: +"Operation to run; help {topic:\"telecom\"} lists each one's arguments"
    • addedInput schema / properties / detail
      Added value: +{
      +  "description": "compact (default) or full",
      +  "enum": [
      +    "compact",
      +    "full"
      +  ],
      +  "type": "string"
      +}
    • addedInput schema / properties / offset
      Added value: +{
      +  "description": "Rows to skip",
      +  "type": "number"
      +}
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "$schema": "http://json-schema.org/draft-07/schema#",
      +  "additionalProperties": {},
      +  "properties": {
      +    "commission_disclosure": {
      +      "type": "string"
      +    },
      +    "cross_border_note": {
      +      "type": "string"
      +    },
      +    "limit": {
      +      "type": "number"
      +    },
      +    "more": {
      +      "description": "How to fetch the next page",
      +      "type": "string"
      +    },
      +    "offset": {
      +      "type": "number"
      +    },
      +    "returned": {
      +      "type": "number"
      +    },
      +    "total": {
      +      "description": "All matches, not just this page",
      +      "type": "number"
      +    }
      +  },
      +  "type": "object"
      +}
  2. Added

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare the operation is read-only, idempotent, non-destructive, and closed-world, so safety is covered. The description adds provenance ('sourced price lists') and the two data modes, but does not clarify pagination, result completeness, or what 'in preparation' means for availability.

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 description is compact and front-loads the two action modes with no filler. However, the opening fragment 'Sourced price lists, in preparation.' is awkward and leaves an important availability caveat unexplained.

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?

With an output schema and full parameter descriptions, the definition need not explain return values or every filter. Still, for a 13-parameter tool it omits sibling routing and does not resolve whether 'in preparation' means incomplete coverage or unavailable data, leaving a meaningful gap.

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%, so the schema already documents all 13 parameters including enums and filter meanings. The description adds a useful high-level mapping from action to relevant filters, but it does not add syntax or constraints beyond that baseline.

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 price lists for home internet and mobile tariffs, and explains the two action modes with their relevant filter categories. It lacks explicit sibling differentiation and the phrase 'in preparation' makes availability slightly ambiguous, so it is clear but not fully polished.

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

Usage Guidelines2/5

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

It only defines the two action values and gives no guidance on when to use this tool rather than sibling tools, nor any prerequisites or exclusions. The internet/mobile split is useful for parameter selection but is not tool-selection guidance.

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