Skip to main content
Glama
Sign In
Axonity Flow MCP Server

Axonity Flow MCP Server

Official
by AxonityAI
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

rotate_webhook_trigger

Rotate a webhook trigger's token to obtain a new plaintext token. The old token remains valid for a short grace period, enabling callers to migrate without disruption.

Instructions

Rotate a webhook trigger's token. Returns the new plaintext token ONCE. The old token keeps working for a short grace period so callers can be migrated.

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": {
      "webhookId": "<webhookId>",
      "confirm": "<confirm>"
    },
    "name": "rotate_webhook_trigger"
  }
}

Input Schema

NameRequiredDescriptionDefault
confirmYesMust be true. Destructive and irreversible — ask your human first.
webhookIdYesThe webhook trigger's id.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

A4/5.0
Behavior4/5

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

Discloses key behaviors: token rotation, one-time return of plaintext, grace period. With no annotations, description carries the burden; it is transparent but could mention that the action is destructive (though confirm param covers it).

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 sentences, no fluff, front-loaded with action. Every sentence adds value.

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?

No output schema, but description explains return value (new token once) and grace period. Lacks error cases or prerequisites, but adequate for a simple mutation tool.

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 covers both parameters (100% coverage). Description adds no additional meaning beyond the schema; the output behavior is described but not parameter-specific.

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?

Clear verb 'Rotate' and specific resource 'webhook trigger's token'. Distinguishes well from sibling tools like list_webhook_triggers, create_webhook_trigger, delete_webhook_trigger.

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?

Describes behavior (new token once, grace period) but does not explicitly state when to use vs. alternatives or prerequisites. No exclusions or comparative guidance.

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