Skip to main content
Glama
TsvetanG2

cognigy-ai-mcp-management-server

by TsvetanG2
OverviewSchemaSourceRelated ServersDiscussions(1)Admin
TypeScript

delete_handover_provider

DestructiveIdempotent

Deletes a Cognigy.AI handover provider, disabling live agent escalation for endpoints using it. Set dryRun=false to confirm deletion.

Instructions

Deletes a Cognigy.AI handover provider. WARNING: Endpoints using this provider will no longer be able to escalate to live agents. MUTATING: Set dryRun=false to delete.

Input Schema

NameRequiredDescriptionDefault
dryRunNoIf true (default), validates without deleting. Set to false to actually delete.
projectIdYesThe project ID the handover provider belongs to
providerIdYesThe handover provider ID to delete

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.2.1
    • addedInput schema / properties / projectId
      Added value: +{
+  "description": "The project ID the handover provider belongs to",
+  "type": "string"
+}
    • changedInput schema / required
      Previous value: -[
-  "providerId"
-]New value: +[
+  "projectId",
+  "providerId"
+]
  2. First observedv0.1.4

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and idempotentHint=true, so the safety profile is covered. The description adds genuinely new behavioral context beyond that: the cascade effect that endpoints using this provider will lose live-agent escalation, plus the dryRun gating. It does not mention permissions or irreversibility beyond the cascade note.

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 short sentences, front-loaded with the action and immediately followed by the highest-risk consequence before the operational detail. No wasted words.

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 delete with no output schema, the description covers the action, the blast radius, and the dryRun safeguard. Combined with 100% schema coverage and destructive annotations, an agent has everything needed to invoke it correctly.

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 projectId, providerId, and dryRun are all fully documented in the schema with the dryRun default. The description restates the dryRun=false requirement but adds no format or syntax detail beyond the schema, so baseline 3 applies.

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?

States a specific verb (Deletes) and resource (Cognigy.AI handover provider), clearly distinguishing it from siblings like update_handover_provider or get_handover_provider. An agent can identify the operation immediately.

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?

The description conveys the safety mechanism (dryRun=false to actually delete) and the consequence, which implies usage context, but it never states when to prefer this over alternatives such as update_handover_provider or when deletion is inappropriate. Usage is implied rather than explicit.

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