Skip to main content
Glama

Account: Get Profile

get_account_profile
Read-onlyIdempotent

[Account] [What it does] Reads the signed-in DSers account's identity, permissions, visible subaccounts, and account settings such as timezone. [When to use] Call it when the user asks about account identity, registration, permissions, or subaccounts. Call it proactively before product, order, or store actions that need a permission check, or before resolving relative dates such as "today" or "this week", which need the account timezone. Trigger words: account, registration, subaccount / staff, permission, timezone. [When not to use] For the current subscription, Credits balance, or plan benefits use get_plan_and_credits; for billing history or invoices use get_plan_and_credit_billing. It cannot read accounts outside your own account tree, and never modifies permissions or subaccounts. [How to use]

  • Empty values carry meaning: an empty subaccount list means it is not visible to the current identity, and an empty menu list means a main account with full access; neither means "none".

  • Convert every time to the account timezone: returned times are UTC, and the response timestamp marks data freshness only, not registration, login, or last-modified time.

  • Partial gaps are not failures: when optional parts are missing, the rest is still reliable, so note what is missing instead of retrying or erroring out.

  • Do not surface raw data: the email address is never returned, only its verification status; store permissions are store IDs, so look up names separately. [Side effects] Read-only. No account data or permission is changed. [Confirmation] None required, the tool is read-only.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
nicknameYesAccount display name
timezoneNoMain account timezone
permissionsYesPermissions of the authenticated account
account_typeYesAccount identity type: main or staff
email_statusYesEmail verification status without exposing the email address
generated_atYesRFC3339 time when this response was generated
sub_accountsYesSubaccounts visible to the authenticated main account
degraded_partsNoOptional account sections that could not be loaded
registration_timeNoRFC3339 registration time
sub_account_countYesNumber of visible subaccounts
toolcall_response_atYesUTC timestamp when the Tool response was returned, formatted as RFC3339.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, but the description adds substantive behavior the annotations cannot convey: empty lists mean 'not visible' rather than 'none', returned times are UTC and must be converted, partial gaps are not failures and should not be retried, and the email is never returned (only verification status). These are non-obvious semantics that directly change how an agent interprets and reports the result.

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?

The bolded section headers make it scan-friendly and the purpose is front-loaded, with every guidance bullet carrying distinct information. The only waste is the closing 'Side effects: Read-only' and 'Confirmation: None required, the tool is read-only' pair, which restates what readOnlyHint already declares and repeats itself internally.

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?

For a zero-parameter read tool with an output schema and full annotation coverage, this covers everything an agent needs: what is returned, how to interpret empty and partial results, timezone handling, and which sibling to use instead. Return-shape detail is correctly delegated to the existing output schema rather than duplicated.

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 in the schema for the description to expand on; the baseline for a zero-parameter tool is a 4. The description correctly adds no invented argument detail and instead spends its words on response interpretation and usage routing.

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 opens with a specific verb and resource ('Reads the signed-in DSers account's identity, permissions, visible subaccounts, and account settings such as timezone'), enumerating exactly which account facets are returned. It distinguishes itself from the adjacent credit/billing tools by name, so an agent can separate this from get_plan_and_credits without opening either schema.

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 provides an explicit 'When to use' section with concrete triggers (identity, registration, permissions, subaccounts) plus proactive-call conditions such as permission checks and resolving relative dates against the account timezone. The 'When not to use' section routes to get_plan_and_credits and get_plan_and_credit_billing and states the scope limit that it cannot read accounts outside the caller's account tree, so the alternatives are named and the boundary is clear.

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.