Skip to main content
Glama

Get My Aukro Account, Profile Stats & Billing Balance

aukro_my_account
Read-onlyIdempotent

Fetches the authenticated user's profile statistics, personal or company settings, addresses, and billing account balance, with optional toggles for billing and personal data.

Instructions

Retrieve the currently authenticated user's profile statistics, personal/company settings, addresses, and billing account balance. Requires authentication.

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

Input Schema

NameRequiredDescriptionDefault
includeBillingNoWhen true, fetches current billing account balance (`/billing/account/balance`)
includePersonalDataNoWhen true, fetches personal/company account settings and addresses (`/users/me/myData`)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint, so the safety profile is fully covered. The description adds the authentication prerequisite and which data sections come back, but gives no detail on behavior when the session is missing/expired or on response shape. Useful but modest added context on top of rich annotations.

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?

Two sentences, zero filler, with the resource scope front-loaded and the authentication constraint trailing as a short caveat. Nothing could be removed without losing information.

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 no output schema, the description carries the burden of describing return content, and it does list the four data groups returned. What's missing is minor: no note on what happens when unauthenticated or whether sections are omitted when the flags are false.

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?

Schema description coverage is 100%, so both includeBilling and includePersonalData are already fully documented including defaults and the endpoints they call. The description's mention of 'personal/company settings, addresses, and billing account balance' loosely echoes the two flags but adds no semantics beyond the schema, making the baseline 3 appropriate.

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 gives a specific verb (Retrieve) and enumerates the resource set: profile statistics, personal/company settings, addresses, and billing account balance, all scoped to 'the currently authenticated user.' That scoping is what separates it from a sibling like aukro_get_user_profile, though it never names that sibling explicitly.

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?

'Requires authentication' is the only usage signal; it implies the caller must already hold a session but says nothing about when to prefer this over aukro_get_user_profile, aukro_auth_status, or aukro_my_bids_and_purchases. Usage is inferable from the name and scope but not stated as guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.