Skip to main content
Glama

Who am I on Spekkr

whoami
Read-onlyIdempotent

Says which Spekkr account the caller is signed in as and which specs it has published. This tool needs sign-in: the first call opens a Spekkr page in the browser, where the person signs in with a code sent to their email address and picks a username if they are new.

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so the safety profile is covered. The description goes beyond that with the non-obvious interaction model: the first call opens a browser page, sign-in uses an emailed code, and a new user picks a username — critical context an agent would otherwise not anticipate. It does not describe how the published-spec list is presented, keeping it below a 5.

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, front-loaded with what the tool returns, followed by the sign-in prerequisite. No filler, hedging, or repetition of annotation data.

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?

For a zero-parameter read tool with no output schema, the description covers return content and the blocking auth flow, which is the main failure mode an agent could hit. Minor gap: it does not say whether a call aborts until sign-in completes or how the result arrives after authentication.

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?

There are zero parameters and the schema coverage is 100%, so the baseline of 4 applies. The description correctly implies no inputs are required, consistent with the empty schema.

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 specific verb and resource: it reports which Spekkr account the caller is signed in as and which specs that account published. This is clearly an identity/ownership read, distinguishable from siblings such as get_spec, check_spec, or publish_spec, which operate on individual specs.

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 implied by the content (call it to learn your identity and published specs), but there is no explicit statement of when to reach for it or when another sibling is preferable. Given there is no close alternative among the listed siblings, the omission is minor but still leaves the agent to infer the trigger condition.

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