Skip to main content
Glama
TopSMS MCP server

TopSMS MCP server

get_pricing

Retrieve current TopSMS SMS pricing by destination zone, volume tier, sender name fee, and billing rules without credentials, so you can quote accurate prices instead of relying on memory.

Instructions

Get the current public TopSMS price list (prices per destination zone, volume tiers, sender name fee, billing rules). Does not require credentials. Use it instead of quoting prices from memory.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_pricing"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.2

TDQS

A4.4/5.0
Behavior4/5

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

With no annotations provided, the description carries the burden and does disclose two non-obvious traits: the data is public/unauthenticated and it is the authoritative current list rather than a cached quote. It stops short of stating currency, whether pricing is account-specific, or the response encoding, which would matter for an agent assembling a price quote.

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

Conciseness5/5

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

Two sentences, no filler, with the resource and its contents front-loaded and the usage directive last. Every clause carries information an agent needs.

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?

For a zero-parameter, no-output-schema lookup, the description adequately conveys the return contents and the auth-free nature. Minor gaps remain around currency, regions covered, and whether the list is scoped to the caller's account.

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?

The tool takes zero parameters, so the schema has nothing to explain; baseline applies. The description correctly implies the call takes no arguments by framing the response as the full public list.

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?

States a specific verb and resource ("Get the current public TopSMS price list") and enumerates the payload contents in the parenthetical: destination zone prices, volume tiers, sender name fee, billing rules. No sibling tool covers pricing, so an agent can route here without opening any schema.

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?

Gives positive guidance ("Use it instead of quoting prices from memory") and removes a common hesitation by stating no credentials are needed. It does not explicitly distinguish this from adjacent financial tools such as get_credit, but the intended usage context is clear.

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