Skip to main content
Glama

Account

get_account
Read-onlyIdempotent

Show which Rainbrand account this session is connected to.

Returns the email and name of the authenticated user behind the session's API key or login. Use it to confirm whose account is active.

Args: (none)

Returns: { "email": string, "name": string | null }

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
llm_modelNoThe model identifier you are running as, for example "claude-opus-4-8" or "gpt-5.2". Omit it or pass "unknown" if you are not certain; the tool runs the same either way. Recorded only for the server developer's analytics.

Output Schema

NameRequiredDescriptionDefault
nameYesName of the authenticated user, or null when not set.
emailYesEmail of the authenticated user.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so the safety profile is covered. The description adds meaningful context beyond that: the identity is derived from the session's API key or login, and the scope is session-bound. It stops short of stating failure modes (e.g., unauthenticated session), which keeps it from a 5.

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?

Front-loaded with the purpose, then scope, then usage, then return shape. The Returns block restates what the output schema already provides, and 'Args: (none)' is both redundant and mildly inaccurate, but overall the text is tight.

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-argument identity lookup with an output schema and full annotation coverage, nothing an agent needs is missing. The description correctly conveys that the call is a safe, session-scoped read.

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 coverage is 100% and the single optional llm_model parameter is fully described in the schema, so the baseline is 3. The description's 'Args: (none)' is slightly at odds with the schema's one optional analytics parameter, though it does not materially mislead since that param is non-behavioral.

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?

States a specific verb and resource ('Show which Rainbrand account this session is connected to') and names the exact payload (email and name of the authenticated user). An agent can distinguish this identity-check tool from resource getters like get_brand without opening the schema.

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

Usage Guidelines4/5

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

Gives an explicit use case: 'Use it to confirm whose account is active.' That is a clear context for invocation, but no exclusions or named alternatives are offered, which is acceptable given the sibling tools all target different resources.

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