Skip to main content
Glama

Compare digital services

digital
Read-onlyIdempotent

Monthly prices of digital services from official price lists. action: compare (AI chat, streaming, music, VPN, cloud, office...), api_costs (AI API cost for a usage), history (plan price changes).

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": "digital"
  }
}

Input Schema

NameRequiredDescriptionDefault
planNoPlan id from compare rows (history)
tierNofree, basic, standard, pro, premium, max
limitNoMax rows
actionYesOperation to run; help {topic:"digital"} lists each one's arguments
detailNocompact (default) or full
localeNoLanguage, e.g. cs
offsetNoRows to skip
countryNoCountry code, e.g. CZ
categoryNoai-chat, ai-api, ai-creative, streaming, music, vpn, cloud, office...
currencyNoCurrency code, e.g. CZK
providerNoProvider (api_costs)
input_tokensNoInput tokens per message
output_tokensNoOutput tokens per message
messages_per_monthNoMessages per month

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. Changed6 schema fields changed
    • addedInput schema / properties / action / description
      Added value: +"Operation to run; help {topic:\"digital\"} lists each one's arguments"
    • changedInput schema / properties / currency / description
      Previous value: -"Currency code"New value: +"Currency code, e.g. CZK"
    • 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"
      +}
    • changedInput schema / properties / plan / description
      Previous value: -"Plan id (history)"New value: +"Plan id from compare rows (history)"
    • 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

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered. The description adds only the provenance detail (official price lists) and the action semantics, and says nothing about pagination behavior via limit/offset, defaults for country/currency/locale, or result ordering. Useful but thin beyond the annotations.

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 compact sentences, front-loaded with the data resource before the action breakdown, with zero filler. The action enumeration is dense but readable; the trailing ellipses in category examples are mildly loose but not wasteful.

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 14 parameters, a full schema and an output schema present, the description does not need to restate field docs or return values. However, for a multi-action tool it does not say that non-applicable parameters are ignored per action, nor which fields identify rows in compare versus history output, leaving some assembly work to the schema and the help tool.

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 every one of the 14 parameters is already documented, and the baseline is 3. The description slightly enriches the action parameter by explaining what each enum value produces (compare categories, api_costs usage cost, history plan price changes), but adds no meaning for provider, input_tokens, messages_per_month, tier or currency beyond the schema text.

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 gives a concrete resource and scope: monthly prices of digital services sourced from official price lists, then splits it into three named operations (compare, api_costs, history). It does not differentiate itself from the heterogeneous sibling set (comparisons, telecom, product, search), so it stops short of a 5, but an agent can tell what this tool returns.

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?

The action list functions as routing guidance: use compare for consumer subscription prices across categories, api_costs for AI API cost given a usage, history for plan price changes. It also points to help {topic:"digital"} for per-action arguments. It gives no when-not-to-use conditions or explicit alternative tool, so it is clear context without exclusions.

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