Skip to main content
Glama

role_create

Create new user roles in Crafty Controller to manage permissions and access control for server administration.

Instructions

Create a new role in Crafty Controller

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
role_dataYesRole configuration data

Implementation Reference

  • The `role_create` tool handler implementation. It uses `client.post` to create a new role with the provided data.
    server.tool(
      "role_create",
      "Create a new role in Crafty Controller",
      {
        role_data: z.record(z.string(), z.unknown()).describe("Role configuration data"),
      },
      async ({ role_data }) => {
        try {
          const data = await client.post("/roles", role_data);
          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. While 'Create' implies a write operation, the description doesn't address critical aspects like required permissions, whether the operation is idempotent, error conditions (e.g., duplicate roles), or what happens on success (e.g., returns a role ID). This leaves significant gaps for an agent to understand the tool's behavior.

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, efficient sentence with zero wasted words. It's front-loaded with the core action and resource, making it easy to parse quickly. Every word earns its place by conveying essential purpose.

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?

For a mutation tool with no annotations and no output schema, the description is insufficient. It doesn't explain what 'role' means in this system, what data should be in 'role_data', what the tool returns, or error handling. Given the complexity implied by nested objects in the schema and the lack of structured guidance, more context is needed for an agent to use this tool effectively.

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 description coverage is 100%, with the single parameter 'role_data' documented as 'Role configuration data' in the schema. The description adds no additional parameter information beyond this, such as example fields or constraints. Given the high schema coverage, the baseline score of 3 is appropriate, as the schema does the heavy lifting.

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 action ('Create') and resource ('a new role in Crafty Controller'), making the purpose immediately understandable. However, it doesn't differentiate this tool from other role-related tools like role_update or role_delete, nor does it specify what distinguishes a 'role' in this context from other entities like users or servers.

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?

No guidance is provided about when to use this tool versus alternatives like role_update or user_create. The description doesn't mention prerequisites (e.g., authentication via crafty_login), use cases (e.g., setting up permissions), or constraints (e.g., role name uniqueness).

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