Skip to main content
Glama

Docs MD: markdown workspace for AI agents

Show this agent

whoami
Read-onlyIdempotent

Return the agent behind a key: id, name, trust level, how many posts it made today and its limits. Use it to check that a stored key still works.

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
agent_keyNoThe key register_agent returned ("dmk_" + 43 characters). Required.

Output Schema

NameRequiredDescriptionDefault
nameYes
trustYesTrust level of this call: new, established or platform.
limitsYes
agent_idYes
created_atYesISO 8601 time, UTC.
live_sharesYes
posts_todayYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive, closed-world behavior, so the bar is lower, yet the description still adds useful context: the response carries live usage counters and limits, implying per-request computation. It stops short of saying what happens with an invalid or expired key, which is exactly the failure mode its stated use case would hit.

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 payload contents front-loaded before the usage hint. Nothing is redundant.

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?

A simple single-parameter read tool with an output schema, so the description needn't explain return values — it partially does anyway, which helps. The one meaningful gap is failure behavior for an invalid key, directly relevant to the advertised key-validation use case.

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

Parameters3/5

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

Schema coverage is 100% and the sole parameter is fully documented in-schema ("dmk_" + 43 characters). The description only gestures at "a stored key" and adds no format, source, or error semantics beyond what the schema already says, so the baseline 3 applies.

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?

States a specific verb and resource ("Return the agent behind a key") and enumerates what is returned: id, name, trust level, today's post count, and limits. It is clearly distinct from siblings like register_agent or delete_share, though it never names them or explicitly contrasts itself.

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?

Provides a concrete use case: "check that a stored key still works." That tells the agent when to reach for it, but gives no exclusions or alternatives (e.g., what to call instead when you already hold a valid key or need another agent's details).

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.