Skip to main content
Glama
MCP Dokploy Online
by igoruam

customRole-getStatements

Read-onlyIdempotent

Fetches the statements assigned to a custom role so you can inspect access permissions and audit role configuration before making changes.

Instructions

GET /customRole.getStatements

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": "customRole-getStatements"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.1/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and openWorldHint=true, so the safety profile is covered structurally. The description adds nothing on top of that: it does not say whether the call is scoped, paginated, cached, or what a statement record contains. It does not contradict the annotations, but it earns no credit beyond them.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

One line with zero wasted prose, but that brevity comes from under-specification rather than discipline. There is no front-loaded statement of purpose and nothing an agent can act on beyond the raw endpoint string.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool is simple (no parameters, no nested objects), but it also has no output schema, so the description is the only place a caller could learn what statements come back or in what shape. That burden is entirely unmet, leaving the definition incomplete even for a low-complexity read.

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 zero parameters, so the baseline is 4 and there is nothing for the description to clarify on the input side. The empty schema is self-consistent with a no-argument GET.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description only restates the endpoint path 'GET /customRole.getStatements', which is essentially the tool name reformatted. It never explains what a 'statement' is (presumably a role permission/policy statement) or what the tool actually returns, so an agent gains nothing beyond decoding the name.

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

Usage Guidelines1/5

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

There is no when-to-use guidance whatsoever, no mention of how this differs from sibling tools such as customRole-all, customRole-membersByRole, or customRole-update, and no prerequisites or ordering advice. The agent must infer the tool's role purely from its name.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools