Skip to main content
Glama

Get cluster role bindings

get_cluster_role_bindings
Read-only

Fetch ClusterRoleBindings and optionally RoleBindings for RBAC analysis. Returns binding name, roleRef (ClusterRole/Role name), and subjects (ServiceAccounts, Users, Groups). Use this to diagnose permission-denied errors - it shows WHO has WHAT permissions. Unlike describe_resource, this can LIST all bindings without knowing names upfront.

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_cluster_role_bindings"
  }
}

Input Schema

NameRequiredDescriptionDefault
namespaceNoIf provided, also fetch namespace-scoped RoleBindings here.
cluster_idYesAnkra cluster id (UUID) the call targets. Discover ids with list_clusters.
subject_nameNoFilter to bindings referencing this subject (e.g. service account name).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, so the safety profile is covered. The description adds what the response contains (name, roleRef, subjects) and the conditional dual-scope behavior of the namespace parameter, which is real added context. It stops short of describing pagination or limits, hence not a 5.

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, each earning its place: what it fetches, what it returns, why/when to use it. The differentiation from describe_resource is placed at the end as a natural closer with zero filler.

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?

There is no output schema, so the description carries the burden of explaining return values — and it does, listing the three returned fields. What it returns and when to use it are both clear; only edge behavior (empty results, large clusters) is unaddressed, which is a minor gap for a read-only list tool.

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% and each parameter already carries a description, so the schema does the heavy lifting. The description's mention of 'optional RoleBindings' echoes the namespace parameter's schema text rather than adding new meaning, though it reinforces the conditional behavior. Baseline 3 applies.

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 verb and resource ('Fetch ClusterRoleBindings and optionally RoleBindings') plus the analysis purpose (RBAC). A reader instantly knows this is a read of RBAC binding objects, not a generic cluster query.

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

Usage Guidelines5/5

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

Gives an explicit use case ('diagnose permission-denied errors') and names the alternative it supersedes ('Unlike describe_resource, this can LIST all bindings without knowing names upfront'). The selection criterion against the closest sibling is spelled out.

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.