Skip to main content
Glama

Get service cluster policy

get_service_cluster_policy
Read-only

Read a cluster's managed-service placement policy (the twin of ankra services policy get): the region and data boundary declared for it, whether its data must stay local, and the revision set_service_cluster_policy needs to change it. A cluster whose organisation never declared one answers that none is declared; its services are then set up under the open default (region and data boundary unspecified, not local-only), which only other undeclared clusters share. Read-only.

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>"
    },
    "name": "get_service_cluster_policy"
  }
}

Input Schema

NameRequiredDescriptionDefault
cluster_idYesCluster id (UUID) from list_clusters.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare `readOnlyHint: true`, and the description adds meaningful behavioral context: what the policy contains, what the revision is for, and how undeclared policies behave. It does not cover error cases or authorization requirements, so it stops short of fully describing behavior.

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?

The purpose and returned fields are front-loaded, and the fallback behavior is explained directly afterward. The final 'Read-only.' sentence is redundant with the annotation and opening verb, and the CLI-twin parenthetical is somewhat extraneous, but the description remains efficient.

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 simple, read-only tool with one required parameter and no output schema, the description supplies the important return semantics and the undeclared-policy fallback. An agent has enough information to select the tool, call it correctly, and interpret the result.

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?

The schema fully documents the single `cluster_id` parameter, including that it comes from `list_clusters`. The description adds no parameter-specific meaning beyond the schema, so the high schema coverage makes 3 the appropriate baseline.

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 read operation over a specific resource: a cluster's managed-service placement policy. It also names the returned policy elements and explicitly distinguishes the tool from `set_service_cluster_policy` by mentioning the revision needed to change it.

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?

The description makes the read use case clear and implies the workflow of retrieving the revision before calling `set_service_cluster_policy`. It does not explicitly state when not to use this tool or compare it against every similar policy-reading sibling, but the context is clear.

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.