Skip to main content
Glama

Balance and prices

my_account
Read-only

Your credit balance, prices and usage. Needs a 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": "my_account"
  }
}

Input Schema

NameRequiredDescriptionDefault
api_keyNoOptional if your client sends Authorization: Bearer sw_agent_...

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

readOnlyHint=true already tells the agent this is a safe read, so the description's main added value is the auth requirement ('Needs a key'). It does not explain what 'usage' or 'prices' cover, whether results are scoped to the authenticated account, or how much data comes back.

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?

Two short sentences, front-loaded with the resources returned and followed by the prerequisite. No filler, though the terseness edges toward under-specification rather than tight writing.

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

Completeness3/5

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

For a simple one-parameter read tool with full schema coverage and a readOnly annotation, the essentials are present. What is missing is any clarification of what the balance/prices/usage payload contains, which matters since there is no output schema.

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?

There is a single parameter with 100% schema coverage, so the schema already explains that api_key is optional when the client sends an Authorization: Bearer header. The description's 'Needs a key' gestures at that but is slightly at odds with the schema's framing of the key as optional, adding little new meaning.

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 concrete resources returned: credit balance, prices and usage. That is enough to separate it from siblings like top_up (a mutation) or check_website, though it never states the verb or that it is a read of the caller's own account.

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 content ('your credit balance'), and the sole guidance offered is the auth prerequisite 'Needs a key'. There is no explicit when-to-use or when-to-prefer-an-alternative statement, for example relative to top_up.

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