Skip to main content
Glama

Create API key

create_api_key

Issues an additional key (up to 50 active; sign-in sessions do not count) for another agent or environment. The key is shown once.

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
nameNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Goes beyond the annotations by disclosing two important behaviors: the key is shown only once, and there is a limit of 50 active keys with sign-in sessions excluded. It does not explain what happens at the limit or whether the secret appears in the response, but the key behavioral traits are covered.

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 tightly written sentences with no wasted words. The most important constraint and the one-time secret exposure are front-loaded.

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

Completeness3/5

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

For a simple one-parameter creation tool, it covers purpose, quota, and the one-time secret display. However, it omits any explanation of the 'name' parameter and does not describe what happens when the active-key limit is reached, leaving meaningful gaps.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema has one optional 'name' string parameter with 0% schema description coverage, and the description does not mention the parameter at all. It leaves the meaning, purpose, and any constraints on 'name' entirely undocumented.

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?

Uses the specific verb 'Issues' with the resource 'key' and clarifies it creates an additional key for another agent or environment. The word 'additional' helps distinguish it from list/revoke siblings, though it does not name those alternatives.

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 a clear use context: creating a key for another agent or environment. It does not explicitly state when not to use it or name revoke/list as alternatives, but the positive guidance is sufficient for the main selection decision.

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.