Skip to main content
Glama

Create caller key

keys_create

Mint a pf_ caller key. The raw key is shown once. Pass this key on every later tools/call. Send it as the caller_key argument.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior4/5

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

Beyond the non-read-only annotation, the description discloses the key prefix, that the raw value is displayed only once (an irreversible retrieval constraint), and that it is required as caller_key for subsequent calls. It stops short of covering scope/permissions of the minted key, expiry, or revocation behavior.

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?

Three short sentences with zero filler, front-loaded with what is created and what the agent must do with the result. Every sentence carries actionable information.

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

Completeness4/5

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

With no parameters and no output schema, the description covers the essential return-value semantics (raw key shown once) and the follow-up contract (caller_key argument), which is what an agent needs to call it correctly. Gaps are limited to lifecycle details like expiry, scope, and sibling disambiguation.

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

Parameters4/5

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

The tool takes zero parameters, so there is nothing for the description to disambiguate. Baseline for a parameterless tool applies, and the description correctly adds no misleading parameter guidance.

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 a specific verb ("Mint") with a specific resource ("pf_ caller key"), including the key prefix, so an agent knows exactly what is produced. It does not differentiate from the sibling "keys.create", which appears to cover similar ground, leaving the agent to guess which one to call.

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?

"Pass this key on every later tools/call. Send it as the caller_key argument." gives explicit downstream usage, which is the main context an agent needs after calling this tool. There is no statement of when not to call it, whether an existing key can be reused, or how to choose between this and the sibling create tool.

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