Skip to main content
Glama

Bind service consumer

bind_service_consumer
Destructive

Bind an application namespace on a cluster as a consumer of managed services (the twin of ankra services consumers bind). A setup is always for named consumers, and the service's connection details are delivered for them. The application must be deployed to that namespace unless allow_planned is true. Pass expected_revision to change an existing binding; omit it to create one. Requires applications.deploy and clusters.operate.

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": {
      "application_id": "<application_id>",
      "cluster_id": "<cluster_id>",
      "namespace": "<namespace>"
    },
    "name": "bind_service_consumer"
  }
}

Input Schema

NameRequiredDescriptionDefault
namespaceYesThe application's namespace on that cluster.
cluster_idYesCluster id (UUID) the application runs on.
local_onlyNotrue when this consumer's data must stay on its own cluster, so only a service on that cluster may serve it. Defaults to false.
allow_plannedNotrue to bind a namespace the application is not deployed to yet. Defaults to false.
application_idYesApplication id (UUID) from list_applications.
expected_revisionNoThe binding's current revision, to change an existing binding. Omit or 0 to create one.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Goes beyond the destructiveHint=true annotation by disclosing the two required permissions (applications.deploy, clusters.operate), the deployment precondition, and the create-versus-modify branch. It still doesn't say what an existing binding loses or how conflicts on expected_revision surface.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Dense and front-loaded: purpose, precondition, create/update switch, then permissions. Minor waste in the parenthetical CLI twin and the slightly cryptic 'A setup is always for named consumers' sentence.

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 mutation tool with no output schema, it covers purpose, prerequisite, create/update routing, and authorization. What happens to an existing binding on success is the remaining gap, but an agent has enough to call 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 coverage is 100%, so all six parameters are already documented in the schema. The description reinforces the expected_revision and allow_planned semantics but adds no new meaning such as revision-mismatch behavior or the effect of local_only.

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: binding an application namespace on a cluster as a consumer of managed services, plus the CLI equivalent. It does not explicitly name the sibling unbind_service_consumer as the inverse, but the operation is unambiguous.

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 real routing guidance: the namespace must already host the application unless allow_planned is true, and expected_revision selects update versus create. It stops short of naming when to prefer the unbind/confirm siblings, so it is clear context without explicit exclusions.

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.