Skip to main content
Glama

HeyIdentity

rotate_signing_key

Destructive

Generates a new RSA signing key for this configuration. overlap=true keeps the previous key published for the configured window; false removes every earlier key immediately. Needs Pro or Enterprise (or Vetted assurance); rate limited per configuration. Returns the current kid and published keys.

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": {
      "configuration_id": "<configuration_id>",
      "overlap": "<overlap>"
    },
    "name": "rotate_signing_key"
  }
}

Input Schema

NameRequiredDescriptionDefault
overlapYestrue keeps the previous key for the overlap window; false drops all earlier keys immediately.
configuration_idYesThe configuration id (from create_tenant or get_tenant).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Goes well beyond the single destructiveHint annotation: it specifies exactly what is destroyed ('removes every earlier key immediately'), the safe alternative (published during overlap window), plan/assurance entitlements, and per-configuration rate limits. It also discloses the return payload (current kid and published keys), which no output schema provides.

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 sentences, front-loaded with the action, then the key behavioral fork, then entitlements/limits and return value. Every clause carries distinct information with no padding or repetition.

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

Completeness5/5

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

For a two-parameter, high-consequence mutation with no output schema, the description covers purpose, destructive consequences, preconditions, throttling, and the return payload. An agent has everything needed to decide whether to call it and what to expect.

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 baseline is 3. The description's overlap explanation largely restates the schema's own overlap description, and configuration_id is not discussed at all beyond being implied by 'this configuration', so little meaning is added beyond structured fields.

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?

Opens with a specific verb and resource — 'Generates a new RSA signing key for this configuration' — which no sibling tool in the list does (the closest, list_signing_keys, only reads keys). The scope is bounded to one configuration, so an agent can immediately tell this is a per-configuration key-rotation mutation.

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 clear preconditions (Pro/Enterprise or Vetted assurance) and rate limiting, plus the decision rule that selects between overlap modes: true keeps the old key published for the window, false drops it immediately. What it lacks is routing guidance against sibling tools (e.g., when to read keys with list_signing_keys first), so it stops short of full when/when-not coverage.

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