Skip to main content
Glama

AgentPixel

by io.agentpixel
OverviewDiscussionsAdmin

Check account identity

whoami
Read-onlyIdempotent

Which account this connection's API key belongs to.

    status is the account state after email confirmation. plan is "free" (the trial plan id) during the 30-day trial,
    paid after the subscription, or unlimited for internal accounts. trial_ends_at is when the trial ends.
    key_prefix is the start of the key, not the key.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
planYes
statusYes
data_kindYes
account_idYes
key_prefixYes
paid_untilNo
next_actionYes
trial_ends_atNo
evaluation_modeYes
resolution_stateYes
evaluation_expires_atNo
evaluation_install_urlNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / additionalProperties
      Added value: +false
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "properties": {
+    "account_id": {
+      "title": "Account Id",
+      "type": "string"
+    },
+    "data_kind": {
+      "enum": [
+        "synthetic",
+        "resolved"
+      ],
+      "title": "Data Kind",
+      "type": "string"
+    },
+    "evaluation_expires_at": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "default": null,
+      "title": "Evaluation Expires At"
+    },
+    "evaluation_install_url": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "default": null,
+      "title": "Evaluation Install Url"
+    },
+    "evaluation_mode": {
+      "title": "Evaluation Mode",
+      "type": "boolean"
+    },
+    "key_prefix": {
+      "title": "Key Prefix",
+      "type": "string"
+    },
+    "next_action": {
+      "title": "Next Action",
+      "type": "string"
+    },
+    "paid_until": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "default": null,
+      "title": "Paid Until"
+    },
+    "plan": {
+      "enum": [
+        "free",
+        "paid",
+        "unlimited"
+      ],
+      "title": "Plan",
+      "type": "string"
+    },
+    "resolution_state": {
+      "title": "Resolution State",
+      "type": "string"
+    },
+    "status": {
+      "title": "Status",
+      "type": "string"
+    },
+    "trial_ends_at": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "default": null,
+      "title": "Trial Ends At"
+    }
+  },
+  "required": [
+    "account_id",
+    "plan",
+    "status",
+    "key_prefix",
+    "evaluation_mode",
+    "data_kind",
+    "resolution_state",
+    "next_action"
+  ],
+  "title": "Whoami",
+  "type": "object"
+}
  2. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already establish readOnly, idempotent, non-destructive behavior, so the bar is lower. The description adds genuinely useful semantics beyond that: what status means (state after email confirmation), what each plan value means (trial 'free' id, 'paid', 'unlimited'), trial_ends_at, and that key_prefix is a truncated prefix and not the secret key.

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?

Purpose is front-loaded in the first line and the remainder is a tight list of field meanings with no filler. The multi-line indented formatting is slightly awkward but the content earns its place.

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?

With an output schema present, the description need not explain return values, yet it adds useful interpretation of the plan/status/trial fields. Combined with full annotations and zero parameters, the definition is essentially complete; only explicit routing guidance 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 per the rubric the baseline is 4. The description's discussion of returned fields is extra rather than parameter documentation, which is fine.

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 opening line states a specific resource ('the account this connection's API key belongs to'), which is clear and distinguishable from all siblings such as create_api_key or check_install. It is not a bare tautology of the name 'whoami', though it does not explicitly contrast itself with any sibling 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?

The description never states when to call this versus alternatives; the agent must infer from the name that this is for verifying identity/account state. There are no prerequisites or exclusions given.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All AgentPixel toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources