Skip to main content
Glama

AgentPixel

by io.agentpixel
OverviewDiscussionsAdmin

Issue private API key

create_api_key

Issue an API key after the email is confirmed.

    Not needed when confirm_signup already returned api_key. Each call issues another key, so call it once.
    Returns the key once. Store it securely and attach it to the connection.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
account_idYesaccount_id returned by signup_free. Example: 3f1c2b9e-1d2a-4c5b-9e8f-0a1b2c3d4e5f
signup_tokenYessignup_token returned by signup_free. It lasts 24 hours.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
prefixYes
api_keyYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / account_id / description
      Previous value: -"account_id returned by signup, not a pixel ID"New value: +"account_id returned by signup_free. Example: 3f1c2b9e-1d2a-4c5b-9e8f-0a1b2c3d4e5f"
    • changedInput schema / properties / signup_token / description
      Previous value: -"Private token returned by signup or confirmation link; never publish it"New value: +"signup_token returned by signup_free. It lasts 24 hours."
  2. Changed7 schema fields changed
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / account_id / description
      Added value: +"account_id returned by signup, not a pixel ID"
    • addedInput schema / properties / account_id / pattern
      Added value: +"^[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12}$"
    • addedInput schema / properties / signup_token / description
      Added value: +"Private token returned by signup or confirmation link; never publish it"
    • addedInput schema / properties / signup_token / maxLength
      Added value: +512
    • addedInput schema / properties / signup_token / minLength
      Added value: +1
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "properties": {
+    "api_key": {
+      "title": "Api Key",
+      "type": "string"
+    },
+    "prefix": {
+      "title": "Prefix",
+      "type": "string"
+    }
+  },
+  "required": [
+    "api_key",
+    "prefix"
+  ],
+  "title": "IssuedKey",
+  "type": "object"
+}
  3. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already declare readOnlyHint=false, idempotentHint=false and destructiveHint=false; the description goes further by concretizing non-idempotency (each call mints an additional key) and by disclosing that the secret is shown only once and must be stored securely. That is real behavioral value beyond the structured hints.

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?

Three short sentences, front-loaded with the action and prerequisite, then the routing rule, then the return/secret-handling caveat. No filler; every sentence carries decision-relevant information.

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?

An output schema exists, so the description need not describe the response body, yet it still flags the one-shot nature of the returned key. With prerequisites, the sibling alternative, and secret handling all covered, nothing needed to call this correctly is missing.

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 description coverage is 100%: account_id and signup_token are already documented, including the token's 24-hour lifetime. The description only reiterates the confirmation prerequisite and adds no format or syntax detail, so the baseline 3 is correct.

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?

Specific verb+resource ('Issue an API key') with an explicit precondition ('after the email is confirmed'). It also names the sibling confirm_signup, letting an agent distinguish this tool from the signup flow without opening either schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

States an explicit when-not condition ('Not needed when confirm_signup already returned api_key') and a call-count constraint ('Each call issues another key, so call it once'). Both the alternative and the selection rule are spelled out rather than implied.

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