Skip to main content
Glama

Account balance and standing

get_account
Read-onlyIdempotent

Balance (micro-dollars), strikes, whether email is verified and a card is on file, auto-recharge settings, and a fresh account_url for the owner.

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
kyaNoWhat this site decided about the agent behind the account, from an apis.io Agent Signup attestation.
handleNo
statusNo
balanceNomicro-dollars
strikesNo
account_idNo
account_urlNo
card_on_fileNo
auto_rechargeNo
email_verifiedNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / properties / kya / description
      Previous value: -"What this site decided about the agent behind the account, from an apis.io Know Your Agent attestation."New value: +"What this site decided about the agent behind the account, from an apis.io Agent Signup attestation."
  2. First observed

TDQS

B3.4/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 safety is covered. The description adds two genuinely non-obvious behavioral facts: the account_url is minted fresh on each call (so it should not be cached or reused) and it is scoped to the owner (auth requirement). It says nothing about failure behavior when unauthenticated, which is the remaining gap.

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?

A single dense sentence-fragment with the most important item (balance) front-loaded and no filler. The telegraphic style omits a leading verb, which makes the opening slightly ambiguous until the field list establishes it as a read.

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, rich annotations, and an output schema that formally defines the return shape, the definition is nearly complete for a simple read. What is missing is caller guidance (when to reach for it versus get_pricing or disable_auto_recharge), which is the only reason it is not a 5.

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 for the description to disambiguate; baseline 4 applies. The description correctly adds no parameter prose and instead spends its words on outputs.

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 enumerates the exact account attributes returned (balance in micro-dollars, strikes, email verification, card on file, auto-recharge, account_url), which tells an agent precisely what resource this reads. It lacks an explicit verb ("get"/"retrieve") and does not distinguish itself from siblings like get_policy or get_pricing, so it stops short of a 5.

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

Usage Guidelines2/5

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

There is no when-to-use guidance, no prerequisites, and no mention of alternatives such as get_pricing for plan/cost questions or disable_auto_recharge for changing the auto-recharge setting it reports. An agent must infer from the field list alone that this is the account-state lookup.

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