Skip to main content
Glama

Unbind service consumer

unbind_service_consumer
Destructive

Remove a consumer binding (the twin of ankra services consumers unbind). A binding an unretired service still uses is refused: retire the service first. Requires applications.deploy.

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": {
      "consumer_id": "<consumer_id>",
      "expected_revision": "<expected_revision>"
    },
    "name": "unbind_service_consumer"
  }
}

Input Schema

NameRequiredDescriptionDefault
consumer_idYesConsumer binding id (UUID) from list_service_consumers.
expected_revisionYesThe binding's current revision from list_service_consumers.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and idempotentHint=false, so the safety profile is covered; the description adds the refusal rule for in-use bindings and the required permission scope (applications.deploy), which annotations cannot express. It does not say what a success returns or whether the removal is recoverable.

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, then the refusal condition, then the permission requirement. Nothing is redundant and the constraint appears before an agent would commit to the call.

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?

For a destructive two-parameter mutation with no output schema, the description covers the action, the blocking precondition, and auth. The remaining gap is behavior on a stale expected_revision (conflict vs. error) and what success yields, neither of which is stated.

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%, and both parameters (consumer_id, expected_revision) are documented in the schema, including where to obtain them via list_service_consumers. The description adds no parameter meaning beyond that, so the baseline of 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource: 'Remove a consumer binding', with the CLI twin `ankra services consumers unbind` as a disambiguating anchor. It is clearly the inverse of bind_service_consumer, but it never names that sibling explicitly, so differentiation is inferential rather than stated.

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 an actionable precondition: a binding still used by an unretired service is refused, so retire the service first. That routes the agent toward retirement flows before calling this. It does not, however, contrast this with sibling alternatives such as confirm_service_disconnection or bind_service_consumer.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.