Skip to main content
Glama

Visibility Genies

Show my account

whoami
Read-only

Shows which account this connection acts as: the email, the token scopes, the account's balance (what is free to spend, or that the account is sponsored and its manager pays), on a paid plan that includes data, the data included in the plan that is left this month, and the agent spend limit per request. Free: buys no data.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
metaNo
modeYes
scopesYes
balanceYes
userEmailYes
creditsRemainingYes
agentSpendLimitUsdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, openWorldHint=false, and destructiveHint=false, so safety is covered. The description goes beyond them by disclosing what identity and quota information is surfaced, including the sponsored-account case where a manager pays and the per-request agent spend limit — context that materially affects how an agent plans calls.

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?

It is a single front-loaded sentence with no filler and no restatement of the title. The middle clause ('on a paid plan that includes data, the data included in the plan that is left this month') is dense and slightly tangled, and the trailing 'Free: buys no data.' is terse to the point of ambiguity, but nothing is wasted.

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?

An output schema exists, so the description need not describe the response shape, and annotations cover the safety profile; with zero parameters the remaining burden is light. It is nearly complete, though it does not mention unauthenticated or invalid-token behavior, which matters for a connection-identity tool.

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?

With zero parameters, the baseline is 4 and there is nothing for the description to clarify. The description adds no parameter detail, but none is needed for a no-argument call.

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 precise verb+resource: 'Shows which account this connection acts as', then enumerates the exact facts returned (email, token scopes, balance, plan data remaining, agent spend limit). This is unmistakably distinct from any of the sibling tools, which all operate on projects, keywords, competitors, or SEO data.

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

Usage Guidelines3/5

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

Usage is only implied: an agent can infer this is a diagnostic/identity check useful before spending or when plan limits are unclear, but the description never says when to call it, when not to, or what to do instead. With no alternatives named and no preconditions stated, this is minimum-viable guidance.

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