Skip to main content
Glama

Set service cluster policy

set_service_cluster_policy
Destructive

Declare a cluster's managed-service placement policy (the twin of ankra services policy set): the physical region it runs in (for example eu-north-1) and the data boundary its data may stay within (for example eu), which decides which consumers a service on it may serve. Declaring one is optional: a cluster without one is set up under the open default (unspecified), and once declared, every setup on the cluster is held to it; unspecified is reserved and cannot be declared. expected_revision is the policy's current revision from get_service_cluster_policy, or 0 to create it. Requires clusters.write.

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": {
      "cluster_id": "<cluster_id>",
      "region": "<region>",
      "data_boundary": "<data_boundary>",
      "expected_revision": "<expected_revision>"
    },
    "name": "set_service_cluster_policy"
  }
}

Input Schema

NameRequiredDescriptionDefault
regionYesPhysical cloud region of the cluster, for example eu-north-1. It locates infrastructure; it is not the data-location promise.
cluster_idYesCluster id (UUID) from list_clusters.
local_onlyNotrue when data on this cluster must stay on it. Defaults to false.
data_boundaryYesBoundary the data is permitted to stay within, for example eu. Sharing a service across clusters is decided by this, never by the region.
expected_revisionYesThe policy's current revision from get_service_cluster_policy; 0 creates a policy and is refused when one exists.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Annotations already flag destructiveHint=true and non-idempotent, and the description goes well beyond them: it discloses the auth requirement ('Requires clusters.write'), the lasting consequence that once declared every setup on the cluster is held to it, and the reserved-value constraint on `unspecified`. The optimistic-concurrency contract for expected_revision is explained rather than left to the annotation alone.

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?

Front-loaded with purpose and packed with substantive detail, with no filler sentences. There is mild duplication in that the region/data-boundary distinction also appears verbatim-ish in the schema property descriptions, and the single dense paragraph is harder to scan than it needs to be.

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?

Covers what an agent needs for a mutating, no-output-schema policy tool: auth, revision concurrency, defaults, and enforcement scope. The remaining gap is the interaction between `local_only` and `data_boundary`, which is described nowhere in either the description or the schema, so an agent must guess how the two combine.

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%, so a 3 is the floor, but the description adds real meaning: it separates region (where infrastructure lives) from data_boundary (which consumers a service may serve), and states that expected_revision is the current revision or 0 to create. It leaves `local_only` entirely to the schema, which keeps it from a 5.

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?

Opens with a specific verb+resource: 'Declare a cluster's managed-service placement policy', and immediately concretizes it with the two dimensions that define the policy (physical region and data boundary). It also distinguishes itself from the read counterpart by naming `get_service_cluster_policy` as the source of `expected_revision`, so an agent can tell set from get without opening a 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?

Explains the optionality model clearly: a cluster without a policy runs under the open `unspecified` default, and `unspecified` cannot be declared. It does not spell out a when-not-to-use case (e.g. that reading first via the get tool is mandatory to obtain a non-zero revision), but the expected_revision=0-to-create rule effectively implies the create-vs-update routing.

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.