Skip to main content
Glama
Pombus MCP Server

Pombus MCP Server

Official

Create API key

create_api_key
Destructive

Mint a new API key for a pod, returning its secret once. Scoped creators can only narrow the new key's permissions, never widen them.

Instructions

Mint a new API key in the pod. The secret is returned once. A scoped creator can only narrow, never widen, the new key's permissions.

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": {
      "pod_id": "<pod_id>"
    },
    "name": "create_api_key"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNo
pod_idYesA pod id the key can reach. The server rejects any id outside this key's scope.
permissionsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and idempotentHint=false, and the description adds two genuinely useful facts beyond them: the secret is returned only once, and a scoped creator can only narrow permissions, never widen them. It still doesn't say what happens on failure or how the key is identified later.

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 short sentences, the one-time secret disclosure is front-loaded, and no wording is wasted.

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 destructive, non-idempotent mutation with no output schema, the description covers the critical irreversibility (secret shown once) and the authorization constraint. It is nonetheless thin on the permissions parameter and on what a successful response contains.

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?

Schema coverage is only 33% – pod_id is documented in the schema, but 'name' and 'permissions' have no descriptions anywhere. 'permissions' is the semantically richest parameter (format, allowed values, defaults, interaction with the narrowing rule) and the description says nothing about it.

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?

States a specific verb ('Mint') and resource ('new API key') scoped to a pod, which distinguishes it from list_api_keys and delete_api_key. It does not explicitly name a sibling, but the create action is unambiguous.

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?

The description never says when to use this versus alternatives (e.g., list_api_keys to inspect existing keys) or what prerequisites are needed. The scoped-creator note is a constraint on the result, not guidance on when to invoke the tool.

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