Skip to main content
Glama

Get User Account

get_user_account
Read-only

The caller's XP account as shown on the XP account page: name, email, wallet, order history and referral stats -- 'my account', 'my referral link', 'how much have I spent?'. Order status is in get_my_orders; delivered tickets are in get_my_tickets. Requires sign-in.

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_user_account"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior4/5

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

The annotations already establish that this is a safe, read-only, closed-world operation. The description adds useful behavioral context beyond them: it requires sign-in and clearly scopes the returned account data. It does not discuss rate limits or partial-account edge cases, but those are not critical here.

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?

The description is front-loaded with the account contents, then gives trigger examples, sibling routing, and the sign-in requirement. Every sentence adds distinct value without repetition or padding.

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

Completeness5/5

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

Because there is an output schema, the description need not explain return values in detail. It covers the key agent-facing context: what the account includes, when to call it, which sibling tools cover adjacent needs, and that authentication is required.

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?

With zero parameters, there is no parameter semantics to document, so the baseline is high. The description appropriately spends no space on parameters and instead focuses on what the account view contains.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific resource (the caller's XP account) and enumerates the exact contents: name, email, wallet, order history, and referral stats. It also gives natural-language trigger phrases that make the tool's purpose immediately recognizable and distinguishes it from sibling tools handling order status and delivered tickets.

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

Usage Guidelines5/5

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

It explicitly names when to use this tool ('my account', 'my referral link', 'how much have I spent?') and routes two related needs to alternatives: order status to get_my_orders and delivered tickets to get_my_tickets. It also states the prerequisite 'Requires sign-in', leaving little ambiguity for agent selection.

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