Caly

Create API key

create_api_key

Create a Caly API key with the chosen permission tiers (default: the tiers this connection has). The answer holds the secret ONCE; tell the user to store it now. A key can never get more permission than the connection that creates it. Expires in 30 days unless expiresInDays or neverExpires is set.

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

Input Schema

Name	Required	Description
`name`	Yes
`tiers`	No	Permission tiers: read, write, destructive, billing, account, team, connections, support, keys.
`neverExpires`	No
`expiresInDays`	No

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 30, 2026

TDQS

A4.4/5.0

Behavior5/5

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

Beyond annotations (which only say non-readonly, non-idempotent, non-destructive), the description adds critical behavioral context: the secret is returned only once, the key cannot exceed the connection's permissions, and the default expiry is 30 days with two parameter overrides. These are exactly the traits an agent needs to call the tool correctly.

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?

Four tight sentences, front-loaded with the purpose and then the essential operational constraints. No filler, and the one-time secret warning is placed prominently where it matters.

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 output schema, the description correctly discloses the key return behavior ('the secret ONCE'). It covers defaults, expiry, and permission limits, though it could mention whether the name must be unique or any rate limiting.

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?

Schema description coverage is only 25%, so the description is responsible for compensating. It explains the default for tiers ('the tiers this connection has'), clarifies the permission ceiling, and documents the expiry semantics for expiresInDays and neverExpires, adding meaningful behavior beyond the bare schema.

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?

The description names a specific verb and resource ('Create a Caly API key') and immediately scopes it with the key concept of permission tiers. It is clearly distinct from sibling tools like list_api_keys, revoke_api_key, and rotate_api_key without needing to enumerate them.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied by the mention of defaults and expiry, but the description never states when to use this tool versus rotate_api_key or revoke_api_key. It provides operational guidance (tell the user to store the secret) rather than explicit routing guidance.

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

All Caly tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?