Skip to main content
Glama

Create an API key

create_api_key

Creates an API key on the connected account for the user's server to call the REST API with, and returns it once. Create one only when the user asks for it or the integration needs it; keys are listed and revoked in the dashboard.

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
nameNoA label to tell the key apart, e.g. "Production".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare a non-read-only, non-idempotent, non-destructive write, so the bar is lower. The description adds two genuinely useful facts beyond them: the key value is returned exactly once (so the agent knows to surface it immediately and that it is unrecoverable), and lifecycle management lives in the dashboard. Missing only expiry, scope/permission, or rate-limit details.

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 with no filler: the first defines the action and its once-only return, the second constrains when to call it. The most decision-relevant constraint (call only on request) is front-loaded in the second sentence rather than buried.

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-optional-parameter creation tool with annotations covering safety and no output schema, the description supplies what is still needed: what is produced and that it is returned once. Nothing an agent needs to call this correctly is absent.

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?

The single parameter has 100% schema description coverage including an example ("Production"), so the schema already carries its meaning. The description does not mention the label at all and adds nothing new about it, so the 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 concrete verb and resource ("Creates an API key") plus the scope ("on the connected account") and the consumer ("the user's server to call the REST API"). The purpose is unmistakable and cannot be confused with the checkout or verification siblings.

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 an explicit gating condition — create only when the user asks or the integration requires it — which prevents speculative key creation. It also points out that listing and revocation happen in the dashboard, implicitly telling the agent this tool cannot do those jobs, though no named alternative tool is offered.

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