Skip to main content
Glama
Sign In
shipmail-mcp

shipmail-mcp

by shipmail-to
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Rotate Webhook Secret

shipmail_rotate_webhook_secret
DestructiveIdempotent

Rotate a webhook signing secret. After the previous secret expires, integrations using it will stop verifying. The new secret is returned once.

Instructions

Rotate a webhook signing secret. Existing integrations using the old secret stop verifying after the previous_secret_expires_at window; treat as destructive. The new secret is returned once and will appear in the conversation log.

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

Input Schema

NameRequiredDescriptionDefault
idYesShipMail resource ID.
idempotency_keyNoOptional idempotency key. If omitted, the MCP server generates one for POST tools.

Output Schema

NameRequiredDescriptionDefault
secretYes
previous_secret_expires_atYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.1.10
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
    • changedOutput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  2. First observedv0.1.9

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already provide destructiveHint=true and idempotentHint=true. The description adds useful behavioral context: old secret stops verifying after a window, new secret returned once and visible in log. No contradiction.

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 concise sentences with no filler. Front-loaded with purpose, then critical behavioral notes. Every sentence adds value.

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?

Given the tool has output schema and annotations, the description covers purpose, destruction, and secret handling. No gaps for agent decision-making.

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 coverage is 100% with clear descriptions for both parameters. The description adds no additional parameter detail beyond what schema provides, meeting baseline but not exceeding.

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 clearly states the verb 'rotate' and the resource 'webhook signing secret', distinguishing it from related tools like create, update, delete webhook. The scope and effect are immediately evident.

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?

The description implies usage context (rotating a secret) and warns of destructive nature, but does not explicitly compare to alternatives or state when not to use. Still, clarity is adequate.

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

Deploy Server

Other Tools