Skip to main content
Glama

Babelii-Diofis Account

Ringkasan akun saya

account_overview
Read-onlyIdempotent

Summary of the connected account: name, language, balance, credit limit, spendable amount, and counts of pending top-ups, active scheduled purchases and unread notifications. 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_overview"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

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.' merely restates structured data and earns no credit. Beyond that, the description adds no behavioral context such as auth requirements, freshness/caching of balances, or error conditions. Its only real addition — the set of fields covered — is also covered by the output schema.

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?

It is a single front-loaded sentence that identifies the tool as a summary immediately and then lists contents, with only the trailing 'Read only.' being redundant filler given the annotations. Slightly list-heavy but no wasted sentences.

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?

With zero parameters, an existing output schema, and rich annotations, little prose is required, and the description covers the aggregate nature of the response adequately. The only shortfall is that it does not hint at data freshness or how counts are scoped (e.g., all-time vs. upcoming), which an agent reading a balance snapshot might want.

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 no parameter meaning to explain and the baseline is 4. The description correctly avoids inventing arguments that would mislead the agent.

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 the resource ('the connected account') and enumerates exactly what the summary contains (name, language, balance, credit limit, spendable amount, and counts of pending top-ups, active scheduled purchases, unread notifications). That field list makes it clearly the aggregate/overview read, distinct in scope from the narrower siblings. It does not, however, explicitly contrast itself with siblings such as account_balance_history or account_notifications, which keeps it at 4.

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: an agent can infer 'call this for a quick aggregate snapshot instead of several narrower account calls', but the description never says when to prefer it over account_balance_history or account_notifications, nor any precondition. The enumerated contents do implicitly signal the breadth of the snapshot, which lifts it above a bare 2.

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