Skip to main content
Glama

MeiSIM USA

My MeiSIM account and balance

get_account
Read-only

Show the MeiSIM account behind your API key: company, status, prepaid wallet balance in USD, and how many new numbers you may still activate today. Use before buy_numbers, or when the user asks what is left. Needs your API key.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
emailYes
statusYes
companyYes
currencyYes
topup_noteYes
balance_usdYes
daily_line_limitYes
lines_remaining_todayYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=true, so safety is covered. The description adds two things the annotations don't: that an API key is required (identity-scoped to the caller's own account) and that the activation count is a daily quota ("may still activate today"). It stops short of noting any rate limits, but with an output schema present the return shape doesn't need spelling out.

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: the first front-loads the returned fields, the second carries usage and the auth requirement. Every clause earns its place and nothing is repeated from the schema or annotations.

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

Completeness5/5

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

For a zero-parameter, read-only lookup with an output schema, the description covers purpose, return fields, calling precondition, and auth needs. An agent has everything required to call it correctly on the first try.

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 there is nothing the description must disambiguate. Baseline 4 applies; the implicit "account behind your API key" framing usefully explains why no account identifier is needed.

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?

Specific verb ("Show") plus a precisely enumerated resource: company, status, prepaid wallet balance in USD, and remaining daily number activations. The field list makes it unmistakable against sibling tools like buy_numbers, list_my_numbers, or topup_lookup.

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

Usage Guidelines5/5

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

"Use before buy_numbers, or when the user asks what is left" gives an explicit precondition plus a conversational trigger, and names the sibling it should precede. That is enough for an agent to route to it without inferring anything.

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.