Skip to main content
Glama

accounts_get_account_info

Read-onlyIdempotent

Retrieve the authenticated account's profile and details from the Aeza API so an AI agent can verify identity and access account data.

Instructions

Get account info GET /accounts/me

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

C2.8/5.0
Behavior2/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered externally. The description adds only the raw endpoint path and nothing about what is returned or any auth/side-effect context, and with no output schema the return behavior is entirely undisclosed.

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?

Two terse lines, front-loaded with the verb and resource, with no filler. The brevity borders on under-specification rather than verbosity, but nothing is wasted.

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

Completeness2/5

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

With no input parameters and no output schema, the description carries the full burden of explaining what 'account info' contains, and it says nothing about returned fields. For a zero-annotation-gap but zero-schema tool, this leaves the agent guessing at the payload it will receive.

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; the baseline applies. The parenthetical endpoint reference is consistent with a no-argument call against the caller's own account.

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

Purpose3/5

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

"Get account info" essentially restates the tool name rather than describing the resource; the appended "GET /accounts/me" endpoint does clarify that it targets the authenticated user's own account, which lifts it above pure tautology. It never distinguishes itself from write counterparts such as accounts_patch_account_me, so the agent must infer the read-only scope.

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 statement of when to call this versus the sibling patch endpoint or other account tools such as accounts_change_password or account_payment_methods_get_list. The agent is left to infer usage purely from the name and annotations.

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

Deploy Server

Other Tools