Skip to main content
Glama

Get cluster access policy

get_cluster_access_policy
Read-only

The organisation cluster access policy (the twin of ankra org access-policy get): the role a cluster's creator receives on it, the highest role any cluster access grant may carry, the longest a grant above view may last, and the role from which grants need a reason; is_configured false means no policy is set and the defaults apply. Also returns the pending policy proposal, if there is one, with its apply_url. The result opens with organisation_id and organisation_name, the organisation that was read: check it is the one you meant before reporting the policy to anyone. Requires kube_access.manage, kube_access.policy or kube_access.elevate. Read-only.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_cluster_access_policy"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior5/5

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

Goes well beyond the readOnlyHint annotation: it explains the is_configured=false default semantics, discloses that a pending proposal and its apply_url may be present, names the audit-relevant verification step on organisation_id, and lists the required kube_access permissions. This is exactly the extra context annotations cannot carry.

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?

Information is front-loaded – the returned fields come first, then defaults, then proposal, then the verification warning and permission requirements. The opening sentence is densely packed with a long field list, but almost every clause earns its place.

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?

There is no output schema, so the description must carry the return shape, and it does: named fields, default behavior, optional proposal data, and envelope fields. Combined with the permission and read-only notes, an agent has everything needed to call and interpret it.

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?

The tool takes no parameters, so there is no input surface for the description to clarify; the baseline for a zero-parameter tool applies. Nothing is misleading or missing on this dimension.

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 and enumerates exactly what the read returns (creator role, max grant role, max duration above view, reason threshold, is_configured, pending proposal). It does not, however, distinguish itself from nearby siblings such as get_service_cluster_policy, which an agent could easily confuse with this one.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Includes useful operational guidance – verify the returned organisation_id is the intended org before reporting, and the three permissions that authorize the call. It stops short of stating when to prefer this over a sibling like get_service_cluster_policy or when the pending-proposal half matters versus a separate call.

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.