Skip to main content
Glama

MaxRechnung

API-Key prüfen (Whoami)

whoami
Read-only

Tarif: in jedem Tarif (Free, Pro, Business).

API-Key prüfen (Whoami)

Validiert den API-Key und gibt das zugehörige Konto (ID, E-Mail, Firma, Tarif) sowie den Key selbst (Präfix, Name, Scopes, Zeitstempel) zurück. Kein Scope nötig — nur ein gültiger Key. Gedacht als Verbindungstest und für das Konto-Label in Integrationen (n8n, Make, MCP …); label ist bereits fertig formatiert (Firma, sonst E-Mail). account.plan ist der Tarif, an dem x-min-plan jeder Operation gemessen wird; account.upgrade_url führt zum Tarifwechsel.

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.6/5.0
Behavior5/5

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

Beyond the readOnly/non-destructive annotations, it discloses the authorization requirement (no scope needed), the exact response payload, that `label` is pre-formatted (company, falling back to email), that `account.plan` is what `x-min-plan` on every operation is measured against, and that `account.upgrade_url` points to a plan change. That is substantive behavior an agent cannot get from the annotations.

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?

Dense but front-loaded and information-rich; every clause carries real content (tier availability, response shape, scope requirement, plan semantics). The only waste is the redundant restatement of the title as "API-Key prüfen (Whoami)" inside the body.

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

Completeness5/5

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

There is no output schema, so the description must carry the return-value burden, and it does: it enumerates the account and key fields, explains `label`, `account.plan`, and `upgrade_url`. For a parameterless diagnostic tool, nothing an agent needs to call or interpret it is missing.

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 the baseline of 4 applies. The description compensates elsewhere by explaining the response fields in detail, which is useful even though it is not strictly parameter semantics.

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 states a specific verb and resource: it validates the API key and returns the associated account (ID, email, company, plan) plus key metadata (prefix, name, scopes, timestamps). This is unmistakably distinct from every sibling, which all operate on invoices, customers, documents, or webhooks.

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?

"Gedacht als Verbindungstest und für das Konto-Label in Integrationen (n8n, Make, MCP …)" gives an explicit intended-use context, and "Kein Scope nötig — nur ein gültiger Key" removes a likely prerequisite confusion. There is no explicit when-not guidance, but with no comparable sibling this is a minor gap.

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