Skip to main content
Glama

role_update

Modify permissions and settings for existing roles in Crafty Controller to adjust user access and capabilities.

Instructions

Update an existing role in Crafty Controller

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
role_idYesRole ID to update
updatesYesRole fields to update

Implementation Reference

  • The handler logic for the role_update tool, which uses the CraftyClient to perform a PATCH request to update a role.
    server.tool(
      "role_update",
      "Update an existing role in Crafty Controller",
      {
        role_id: z.string().describe("Role ID to update"),
        updates: z.record(z.string(), z.unknown()).describe("Role fields to update"),
      },
      async ({ role_id, updates }) => {
        try {
          const data = await client.patch(`/roles/${role_id}`, updates);
          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?

With no annotations provided, the description carries the full burden of behavioral disclosure. It states this is an update operation but doesn't mention what permissions are required, whether changes are reversible, what happens to unspecified fields, or any rate limits. This leaves significant gaps for a mutation tool.

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 that gets straight to the point with zero wasted words. It's appropriately sized for a simple update operation and front-loads the essential information.

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 inadequate. It doesn't explain what the tool returns, what errors might occur, or important behavioral aspects like authentication requirements. Given the complexity of updating roles in a controller system, more context is needed.

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%, so the schema already documents both parameters thoroughly. The description doesn't add any additional meaning about the parameters beyond what's in the schema, such as explaining what fields can be in 'updates' or providing examples.

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 ('Update') and target resource ('an existing role in Crafty Controller'), making the purpose immediately understandable. However, it doesn't differentiate this tool from sibling tools like 'user_update' or 'server_update' beyond specifying it's for roles.

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. While the description implies it's for updating roles, there's no mention of prerequisites (e.g., needing an existing role_id), when not to use it, or how it differs from similar update tools for users or servers.

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