Skip to main content
Glama

Babelii-Diofis Account

Top-up saya

account_topups
Read-onlyIdempotent

The account's top-up requests, newest first, with amount and status (pending, paid, failed, expired, cancelled). Up to 50 rows; pass next_before_id as before_id for the next page. Read only.

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

Input Schema

NameRequiredDescriptionDefault
limitNo
before_idNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the closing 'Read only' only restates them. The description does add behavior beyond annotations: newest-first ordering, the 50-row cap, and the cursor mechanism for paging.

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?

Three compact clauses; ordering, fields, paging and safety are each stated once with no filler. Information is front-loaded on what the tool returns, with paging details following.

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?

An output schema exists, so return values need no explanation, and the description still covers ordering, page size and continuation. Missing is the limit default and how to start from the first page, minor but not fully covered.

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?

With 0% schema description coverage, the description must carry the parameters. It explains before_id well via the next_before_id paging instruction and implies limit is capped at 50, but the limit parameter itself, its default of 20, and the cursor's null meaning are never stated.

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?

Names a specific resource ('the account's top-up requests') and adds ordering plus the returned fields (amount, status) with the full status vocabulary. It does not explicitly contrast itself with sibling account_* list tools, but the purpose is unmistakable without opening the schema.

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?

Gives concrete pagination mechanics ('pass next_before_id as before_id for the next page') and states the 50-row page ceiling, which is real operational guidance. It stops short of saying when to reach for this versus related tools such as account_balance_history, so usage is only implied by the topic.

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