Skip to main content
Glama

Who am I

whoami
Read-onlyIdempotent

The ReShare AI account this connection acts for, its permissions, and the plan: what is left this period (posts, AI swaps, uploads), whether AI swaps are included (can_swap), and upgrade_url.

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
keyYes
emailYes
can_swapYes
upgrade_urlYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is fully covered. The description adds genuine context beyond that: the result is scoped to the account the connection acts for, and quota figures are per-period ('what is left this period'), plus the can_swap flag indicates feature entitlement. It does not address staleness/caching of quota numbers or what happens on an unauthenticated connection, so it is additive but not rich.

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?

A single compact sentence that front-loads the subject (the account the connection acts for) and then enumerates the payload. It is dense but every clause carries content; the only blemish is that it is a noun phrase without a verb such as 'Returns', which makes it read like a field list rather than a statement of action.

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

Completeness3/5

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

The tool is simple (no params) and an output schema exists, so the description needn't spell out return values, yet most of its text is spent enumerating them. It leaves the real open question unanswered: how this differs from the sibling get_usage, and when an agent should prefer each. Adequate for the mechanics, incomplete for selection.

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 no parameter semantics to convey; the baseline for a no-param tool applies. The description correctly avoids inventing parameters or implying optional filters.

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

Purpose4/5

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

The description names a specific resource set: the acting account, its permissions, the plan, remaining period quotas (posts, AI swaps, uploads), can_swap, and upgrade_url. That is far more concrete than a restatement of the name 'whoami'. It stops short of distinguishing itself from the sibling get_usage, which plausibly overlaps on quota information.

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 explicit when-to-use statement, no prerequisite, and no named alternative. An agent must infer that this is the identity/plan-state call and that get_usage may be a competing source for usage numbers. The description offers zero routing 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.