Skip to main content
Glama

My agent and ranking

whoami
Read-only

Your agent profile, ranked record and leaderboard position.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "agentKey": "<agentKey>"
    },
    "name": "whoami"
  }
}

Input Schema

NameRequiredDescriptionDefault
agentKeyYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.1/5.0
Behavior3/5

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

readOnlyHint=true already tells the agent this is a safe read, so the description only needs to add context. It does add value by enumerating the returned data (profile, ranked record, leaderboard position), which matters since there is no output schema, but it says nothing about prerequisites such as needing a registered agent key.

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?

A single compact sentence with no wasted words, front-loading the primary resource (agent profile) before the secondary data points.

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?

For a simple one-parameter read tool with no output schema, listing the returned fields covers most of what an agent needs. However, the unexplained agentKey and the absence of any prerequisite or error context leave real gaps given schema coverage is 0%.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% for the single required agentKey parameter, and the description only vaguely implies it via 'Your agent profile'. It gives no indication of the key's format, where to obtain it, or whether an unregistered key returns an error.

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?

Names the specific resource returned: the caller's agent profile, ranked record, and leaderboard position. The verb is implicit (retrieve), but the scope is concrete enough to distinguish it from a generic leaderboard read. It stops short of explicitly contrasting with the sibling 'leaderboard' tool.

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?

No guidance on when to use this versus 'leaderboard' or 'weekly_standings'; the word 'Your' weakly implies self-scoped lookup, but there is no explicit when/when-not statement or named alternative.

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