Ankra

Confirm service disconnection

confirm_service_disconnection

Destructive

Confirm a prepared disconnection and take the application environment off the managed service (step two of a disconnect). The digest must be the one prepare_service_disconnection returned: a plan that changed since, or that expired, is refused. The service stops being connected to the application at once; the application keeps working until it is deployed again, and Ankra removes its connection Secret once no pod reads it. The shared credential is not revoked. Reconnecting needs a new review. Requires applications.deploy, clusters.operate on the service's cluster and clusters.operate and clusters.read on the application's.

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": {
      "instance_id": "<instance_id>",
      "disconnection_id": "<disconnection_id>",
      "digest": "<digest>"
    },
    "name": "confirm_service_disconnection"
  }
}

Input Schema

Name	Required	Description
`digest`	Yes	The disconnection's digest from prepare_service_disconnection.
`instance_id`	Yes	Service instance id (UUID).
`disconnection_id`	Yes	Disconnection id (UUID) from prepare_service_disconnection.

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 1, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Well beyond the destructiveHint=true / idempotentHint=false annotations, the description discloses the actual blast radius: the service unlinks immediately, the application keeps running until redeployed, the connection Secret is removed only when no pod reads it, and the shared credential is NOT revoked. It also notes reconnection requires a fresh review and lists the exact RBAC permissions required on both the service's cluster and the application.

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?

Front-loaded with purpose and step position, then the digest constraint, then consequences, then permissions — each sentence carries distinct information with no repetition of the schema or annotations.

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, non-idempotent mutation with no output schema, the description covers prerequisites, credential requirements, side effects, secret cleanup timing, and irreversibility of the connection. Nothing an agent needs to call it safely is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% and each parameter is described, so the baseline is 3; the description earns an extra point by adding the digest's validity semantics — it must be the exact digest returned by prepare, and stale or expired digests are rejected. It still adds nothing about the two UUID parameters beyond what the schema says.

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 (confirm) plus resource (a prepared disconnection) and explicitly positions itself as 'step two of a disconnect,' which separates it from prepare_service_disconnection and from sibling confirm_* tools like confirm_service_setup/retirement. An agent knows exactly which operation this performs without opening the schema.

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: the digest must come from prepare_service_disconnection, and a changed or expired plan is refused, so the agent knows the ordering constraint. It does not explicitly say when to prefer confirm_service_retirement or how to recover from a refused digest (re-prepare), leaving a small gap.

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

All Ankra tools Inspect

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.