permissions_getResolve the current caller’s permissions and inherited roles, including OIDC group access, to determine allowed actions and object-level visibility.
Resolve caller permissions and role inheritance
Self-service: returns permissions for the current subject and its OIDC groups. Lists elsewhere are filtered per object.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v0.4.3Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
While annotations cover safety (readOnlyHint: true), the description adds valuable context by specifying that it resolves permissions for the 'current subject and its OIDC groups,' clarifying the data focus beyond mere operation safety.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The definition is extremely concise, using two sentences to cover purpose, scope, and differentiation. There is zero wasted language, and the structure is logical.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a tool with zero parameters, the description is completely sufficient for an agent to determine applicability and function accurately.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The tool has zero parameters, meaning the description cannot elaborate on input parameters. Baseline for 0 parameters is 4, and the description adds context about the scope of the retrieved data.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description uses specific language ('Resolve caller permissions and role inheritance') defining the action and the exact resource. It clearly states the tool's function without ambiguity.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
It provides exceptional guidance by defining its scope ('Self-service') and, critically, contrasting its behavior with sibling tools ('Lists elsewhere are filtered per object'), instructing the agent on when to use it and when to avoid it.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.