Skip to main content
Glama
Sign In

Proof Holdings

by holdings.proof
OverviewDiscussionsAdmin

rotate_callback_secret

Destructive

Rotate a sub-account's callback signing secret — the secret that signs every callback_url delivery of its verification requests — and return the new one. This is the only time it is returned, so store it now. Callback deliveries already queued keep the secret they were signed with. An account still delivering through its settings webhook URL is switched over to webhook endpoints first.

ACCESS: needs a Proof account. Authenticate this client (Claude Code: /mcp → Authenticate), then call this tool again. start_login does NOT open this tool.

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

Input Schema

NameRequiredDescriptionDefault
profile_idYesSub-account (profile) ID, 24 hex characters

Output Schema

NameRequiredDescriptionDefault
secretNoSigns every `callback_url` delivery of this sub-account's verification requests (`X-Proof-Signature`).
profile_idNoThe sub-account (`PublicProfile._id`) whose secret this is

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior5/5

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

Goes well beyond the destructiveHint=true annotation: it discloses that the secret is returned only once and must be stored immediately, that already-queued deliveries retain their old signing secret, and that the account is migrated onto webhook endpoints as a side effect. The auth/authentication requirement is also spelled out, which annotations do not cover.

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?

Front-loaded with the core action and the irreversible one-time return warning, then side effects, then access prerequisites. The ACCESS block is somewhat verbose but contains genuinely necessary gating information, so little is wasted.

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 destructive one-parameter mutation with an output schema, the description covers everything an agent needs: what is rotated, that the value is shown once, what happens to in-flight deliveries, the migration side effect, and the authentication gate. Return-value detail is correctly left to the output schema.

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?

The single parameter is fully documented in the schema (24-hex sub-account profile ID) at 100% coverage, so the description adds no parameter detail and none is needed. Baseline 3 applies when the schema carries the semantics.

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?

Names a specific verb+resource combination ('Rotate a sub-account's callback signing secret') and immediately qualifies what that secret is ('signs every callback_url delivery of its verification requests'), which distinguishes it from the sibling rotate_webhook_endpoint_secret. The agent knows exactly what will change and what will be returned.

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 strong situational context: use it when you need a new callback signing secret, and it explains the precondition that settings-webhook accounts are migrated to webhook endpoints first. It also states the auth prerequisite (Proof account, must authenticate this client first, start_login is insufficient). It stops short of explicitly contrasting with rotate_webhook_endpoint_secret, so an agent must infer that endpoint-level rotation is a separate tool.

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

All Proof Holdings toolsInspect
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