Skip to main content
Glama

Axad

My Axad account

get_account
Read-only

Return the learner's Axad account: their plan, its limits and what they use of them (cards in the bag, active lessons), and their credit spent and allowance.

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

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?

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds useful scope detail about what the returned snapshot contains, but says nothing about authorization requirements, freshness of the counters, or what happens if no account/plan exists. Note the idempotentHint=false is consistent with returning a mutable usage snapshot rather than contradicting the description.

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 front-loaded sentence with the resource first and the enumerated contents after. The parenthetical examples ('cards in the bag, active lessons') earn their place by clarifying what 'limits' means, and there is no filler.

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 and no output schema, the description carries the burden of describing the return payload, and it does enumerate the main fields (plan, limits, usage, credit spent/allowance). Absent an output schema, it could go slightly further on structure or edge cases, but it is adequate for a simple self-scoped read.

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 no parameters, so there is nothing for the description to disambiguate; the baseline of 4 applies. The description instead spends its words on the return payload, which is the relevant concern here.

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?

Specific verb and resource ('Return the learner's Axad account') with an enumeration of the contents: plan, limits, consumption (cards in bag, active lessons), credit spent and allowance. It is plainly distinct from the content-oriented siblings (show_quiz, due_cards, list_lessons), though it never explicitly contrasts itself with any of them.

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 or when-not-to-use guidance, no mention of prerequisites, and no reference to any alternative tool. An agent must infer from the purpose alone that this is the tool for account/plan/credit state rather than for lesson or card content.

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.