Retrieves a global Semaphore UI role by slug to inspect its permissions; availability depends on edition, license, and access rights.
get global role. Availability depends on Semaphore edition, license, and permissions; some Community routes return 404 or empty lists. GET /roles/{role_slug}.
| Name | Required | Description | Default |
|---|---|---|---|
| role_slug | Yes |
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already cover read-only, idempotent, non-destructive behavior. The description adds valuable failure-mode context by noting edition/license/permission dependence and possible 404 or empty-list responses, which an agent needs to interpret outcomes. It does not contradict any annotation.
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 description is short, front-loaded, and free of filler. Each sentence adds either the resource/route, availability caveats, or failure-mode context.
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?
It covers availability caveats well, but with no output schema and no parameter documentation, it leaves the agent without guidance on what a successful response looks like or how to obtain a valid role_slug. Adequate but with clear gaps for a single-resource fetch tool.
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?
Schema description coverage is 0%, and the description does not explain what role_slug means, where to source it, or whether it is a slug versus an ID. The route path /roles/{role_slug} only restates the parameter name and does not compensate for the missing semantic detail.
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 states a specific verb and resource ('get global role') and includes the underlying route GET /roles/{role_slug}. It implicitly distinguishes a single-role fetch from list_global_roles, but does not explicitly name or contrast with any sibling tool.
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 gives useful contextual guidance that availability depends on edition, license, and permissions, and that some Community routes return 404 or empty lists. However, it does not say when to prefer this tool over list_global_roles or get_project_role, nor does it explain prerequisites for obtaining a valid role_slug.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.