Skip to main content
Glama

Show my account

get_account
Read-onlyIdempotent

Read your dashboard-visible profile, workspace memberships and linked accounts. This always reads your own account, never another user's, and requires no workspace membership. Credentials and dashboard-hidden provider data are omitted.

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

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior4/5

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

The annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds value the annotations cannot: a confidentiality guarantee ('credentials and dashboard-hidden provider data are omitted') and the fact that no workspace membership is needed. It says nothing about latency or rate limits, but for a zero-argument self-read those are minor.

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 scope and the always-own-account constraint front-loaded before the confidentiality note. Every clause carries information an agent could act on.

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 wisely summarizes the return contents (profile, memberships, linked accounts) and flags what is redacted, which is the main completeness risk here. A short note on whether memberships or linked accounts can ever be empty would close the remaining gap, but nothing essential is missing.

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 and the schema is an empty closed object, so there is no parameter semantics to explain. The description correctly avoids inventing arguments and instead clarifies the implicit 'whose account' question the empty schema leaves open.

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 ('Read your dashboard-visible profile, workspace memberships and linked accounts') and enumerates exactly what is returned. That enumeration separates it from nearby readers such as get_workspace and get_email_preferences without needing to name them.

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?

'This always reads your own account, never another user's' gives an explicit scope boundary, and 'requires no workspace membership' states a precondition an agent would otherwise have to guess. It stops short of pointing to any alternative tool for reading someone else's account, which keeps it below a 5.

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