Skip to main content
Glama

agent-tools (x402 + MCP + A2A directory)

create_api_key

Create a free account API key. No sign-up, email or existing key needed.

The key is returned once and cannot be recovered. Store it in your secret
store; do not print it back to the user or write it to logs. Send it as
`Authorization: Bearer <key>` (or the `api_key` argument where offered) to
get complete `directory_stats` lists, run paid verifications and claim
your own listings. The claim and listing tools read the key only from the
Authorization header; without header support use the REST claim API. Shares the HTTP limit of POST /api/v1/keys (a few keys
per IP per day).

Args:
    name: Optional label to recognise the key later, e.g. your agent name.

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": "create_api_key"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoOptional label to recognise the key later, e.g. your agent name.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Annotations only say it is non-read-only, non-destructive, non-idempotent; the description adds the crucial facts that the key is returned once and unrecoverable, must be stored and not printed or logged, and is rate-limited to a few keys per IP per day. It also discloses that claim and listing tools read the key only from the Authorization header, which is behavior no annotation conveys.

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?

Front-loaded with purpose in the first sentence, then security handling, then auth mechanics, then limits. Slightly padded by the parenthetical header/argument aside and a duplicated arg note, but every paragraph carries usable 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?

For a one-parameter creation tool with an output schema, the description covers everything an agent needs: that the secret is single-shot, how to transmit it, what it unlocks, header-only constraints on downstream tools, and the rate limit. Return-value format is correctly left to the output schema.

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 single optional `name` parameter is documented identically in both schema and description (including the 'your agent name' example), so the description adds no meaning beyond structured fields. Baseline 3 applies.

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?

States a specific verb and resource ('Create a free account API key') and immediately scopes it ('No sign-up, email or existing key needed'), which no sibling tool offers. An agent can tell this apart from register, claim_service_url, or prepare_paid_verification without opening a schema.

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?

Gives concrete downstream uses that justify calling it: complete directory_stats lists, paid verifications, and claiming listings, plus a fallback path (REST claim API) when headers are unavailable. It stops short of saying 'do not call this if you already hold a key', which matters given the per-IP daily limit.

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.