Skip to main content
Glama
TopSMS MCP server

TopSMS MCP server

get_credit

Retrieve your current SMS credit balance and per-message price in your account currency (EUR or CZK) to check available sending budget before purchasing or sending messages.

Instructions

Get the current TopSMS credit balance and the price per SMS, both in your account currency (field currency: EUR for topsms.eu accounts, CZK for topsms.cz accounts).

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_credit"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.2

TDQS

A3.9/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full burden and does disclose the return payload: credit balance, price per SMS, and a currency field whose value depends on the account domain (EUR for topsms.eu, CZK for topsms.cz). It does not explicitly state that the call is read-only or has no side effects, but the 'Get ... current' phrasing and enumerated outputs convey behavior well for a parameterless read.

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?

A single sentence with the two returned values front-loaded and the currency caveat tucked into a parenthetical. Nothing is wasted and there is no filler preamble.

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 read tool with no output schema and no annotations, the description covers what is returned and how currency varies by account. The one gap is sibling differentiation against get_pricing, which would matter for selection but not for correct invocation.

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 per the baseline this scores 4. The description correctly adds no parameter guidance, and the currency parenthetical is a return-value note rather than a parameter claim.

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 a specific verb and two concrete resources: the current TopSMS credit balance and the price per SMS. It is clear what the tool returns, but it never distinguishes itself from the sibling get_pricing, which plausibly returns overlapping pricing information.

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?

Usage is only implied by the phrasing 'current ... balance' — an agent can infer this is the balance-check tool. There is no statement of when to prefer get_credit over get_pricing, nor any preconditions or exclusions, so routing still requires inference.

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