Skip to main content
Glama

role_get

Retrieve detailed information about a specific role by providing its unique ID. Use this tool to access role configurations and permissions within the crafty controller system.

Instructions

Get details for a specific role

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
role_idYesRole ID

Implementation Reference

  • The implementation of the role_get MCP tool, which retrieves role details from the Crafty Controller.
    server.tool(
      "role_get",
      "Get details for a specific role",
      { role_id: z.string().describe("Role ID") },
      async ({ role_id }) => {
        try {
          const data = await client.get(`/roles/${role_id}`);
          return { content: [{ type: "text", text: JSON.stringify(data, null, 2) }] };
        } catch (error) {
          const msg = error instanceof Error ? error.message : String(error);
          return { content: [{ type: "text", text: `Error: ${msg}` }], isError: true };
        }
      }
    );
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states 'Get details' which implies a read-only operation, but it does not specify if authentication is required, rate limits, error handling, or what happens if the role_id is invalid. This leaves gaps for a tool that likely involves data retrieval.

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?

The description is a single, direct sentence with no wasted words. It is front-loaded with the core action ('Get details'), making it easy to scan and understand quickly. Every part of the sentence contributes to the purpose.

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

Completeness3/5

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

Given the tool's simplicity (one parameter, no output schema, no annotations), the description is minimally adequate. It states what the tool does but lacks details on behavior, output format, or error cases. For a read operation with no structured output, more context on return values would improve completeness, but it meets the basic threshold.

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?

The input schema has 100% description coverage, with 'role_id' documented as 'Role ID'. The description adds no additional meaning beyond this, such as format examples or sourcing instructions. With high schema coverage, the baseline is 3, as the schema adequately covers parameter semantics without extra description input.

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?

The description clearly states the verb ('Get') and resource ('details for a specific role'), making the purpose understandable. It distinguishes from siblings like 'role_list' (which lists roles) and 'role_update' (which modifies roles). However, it could be more specific about what 'details' include, such as permissions or metadata.

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternatives. It does not mention prerequisites (e.g., needing a valid role_id), exclusions, or comparisons to siblings like 'role_list' for listing all roles or 'user_get' for user details. Usage is implied but not explicitly stated.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/HadiCherkaoui/crafty-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server