Skip to main content
Glama
Sign In
MCP Hub

MCP Hub

by airano-ir
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

manage_api_keys_create

Create a new API key for a project with defined access scopes and optional expiration; use a project ID or "*" to cover all projects.

Instructions

Create a new API key for a project.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "project_id": "<project_id>"
    },
    "name": "manage_api_keys_create"
  }
}

Input Schema

NameRequiredDescriptionDefault
scopeNoAccess scope - single ("read", "write", "admin") or multiple space-separated ("read write admin") Examples: "read", "write", "admin", "read write", "read write admin"read
project_idYesProject ID or "*" for all projects
descriptionNoOptional description for the key
expires_in_daysNoOptional expiration in days (default: never expires)

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv3.14.0
  2. Removedv3.13.1
  3. First observedv3.4.0

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden but only says it creates a key. It omits important traits for a credential-minting mutation: whether the secret is returned once and unrecoverable, default scope behavior even though the schema defaults to "read", permission requirements, and rate limits.

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?

A single front-loaded sentence with no filler or redundancy. It is efficient, though its brevity reflects under-specification rather than tight editing of rich content.

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

Completeness2/5

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

An output schema exists, so return values needn't be explained, but for a security-sensitive mutation with zero annotations the definition should disclose the one-time secret display and default scope implications. As written, the agent lacks the context needed to use the result safely.

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%, so scope, project_id, description, and expires_in_days are already fully documented. The description adds only the "for a project" framing, which is already implied by the required project_id parameter, so baseline 3 is appropriate.

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 description states a specific verb and resource ("Create a new API key") and scopes it to a project, which is enough for an agent to distinguish it from delete/revoke/rotate/list siblings by name alone. It stops short of explicitly contrasting with those siblings, so it is clear but not maximally differentiating.

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?

There is no guidance on when to create a new key versus rotating an existing one, nor any prerequisites or prerequisites on project access. The agent must infer the use case entirely from the name.

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

Deploy Server

Other Tools