Skip to main content
Glama

account

Read-onlyIdempotent

Which somewhere.cloud account is this session connected as? Takes no arguments and reads only the caller's own account.

It answers "who am I connected as" without a guessed route or an identity inferred from the project list.

Example:

{}
// Returns: { "id": "u_abc", "email": "alice@example.com", "name": "Alice",
//            "anonymous": false, "email_verified": true, "tier": "builder",
//            "summary": "Connected as Alice (alice@example.com). The email address is verified." }

This is the DEVELOPER ACCOUNT holding the projects. For the end user of a customer's app, auth_me with that user's app token answers instead.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

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 and idempotentHint, but the description adds substantive context the annotations cannot: it is the developer account holding the projects, identity is not inferred from a project list, and it includes a concrete return payload with fields such as anonymous, email_verified, and tier. That is real behavioral disclosure, not restatement.

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 answer is front-loaded and the routing note about auth_me is placed well. The middle sentence ('without a guessed route or an identity inferred from the project list') is slightly promotional and the inline example, while useful, is longer than needed for a no-argument call, but nothing is genuinely wasteful.

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?

No output schema exists, yet the example return object documents the key fields including the anonymous and email_verified flags, and the developer-vs-end-user distinction covers the main ambiguity for this complexity level. An agent has everything needed to call and interpret it.

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 has zero parameters, so the baseline is 4. The description confirms 'takes no arguments,' which matches the empty schema exactly, though it adds no further parameter information because none exists to add.

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?

Opens with a specific question-form verb and resource ('Which somewhere.cloud account is this session connected as?') and immediately narrows scope with 'reads only the caller's own account.' It explicitly separates itself from auth_me, which serves the end user of a customer's app, so the agent can distinguish the two 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?

States the invocation constraint ('takes no arguments'), the read scope (caller's own account), and names the alternative tool plus the exact condition that selects it ('For the end user of a customer's app, auth_me with that user's app token answers instead'). Both when-to-use and when-not-to-use are explicit.

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