Skip to main content
Glama

role_delete

Remove roles from Crafty Controller by specifying the role ID to manage user permissions and access control.

Instructions

Delete a role from Crafty Controller

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
role_idYesRole ID to delete

Implementation Reference

  • The "role_delete" tool is registered and implemented as a handler within the registerRoleTools function in src/tools/roles.ts. It takes a role_id argument and performs a DELETE request via the CraftyClient.
    server.tool(
      "role_delete",
      "Delete a role from Crafty Controller",
      { role_id: z.string().describe("Role ID to delete") },
      async ({ role_id }) => {
        try {
          const data = await client.delete(`/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 full burden for behavioral disclosure. While 'Delete' implies a destructive mutation, the description doesn't specify critical behavioral aspects: whether deletion is permanent or reversible, what permissions are required, whether it affects associated users or servers, or what the response looks like (confirmation, error messages). This leaves significant gaps for a destructive operation.

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, focused sentence that states the core functionality without unnecessary words. It's front-loaded with the key action and resource, making it immediately scannable. Every word earns its place in conveying the 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 destructive mutation tool with no annotations and no output schema, the description is insufficiently complete. It doesn't address critical context: what happens post-deletion, error conditions, permission requirements, or system impact. The agent lacks necessary information to use this tool safely and effectively in a production environment.

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_id' clearly documented in the schema. The description adds no additional parameter information beyond what's in the schema (no format examples, constraints, or relationship to other tools). This meets the baseline expectation when schema coverage is complete.

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 ('Delete') and resource ('a role from Crafty Controller'), making the purpose immediately understandable. It distinguishes itself from sibling tools like role_get, role_list, and role_update by specifying the destructive delete operation. However, it doesn't explicitly differentiate from user_delete or server_delete, which are similar destructive operations on different resources.

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 doesn't mention prerequisites (e.g., whether the role must be unused), consequences (e.g., what happens to users assigned this role), or alternatives (e.g., role_update for modification instead of deletion). The agent must infer usage from the tool name alone.

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