Skip to main content
Glama

user_update_permissions

Modify user access controls and server-specific permissions in the Crafty controller system. Change authorization settings for individual users to manage their operational capabilities.

Instructions

Update a user's Crafty and per-server permissions

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
user_idYesUser ID
permissionsYesPermission configuration to update

Implementation Reference

  • The handler function for the `user_update_permissions` tool, which patches user permissions via the client.
    server.tool(
      "user_update_permissions",
      "Update a user's Crafty and per-server permissions",
      {
        user_id: z.string().describe("User ID"),
        permissions: z.record(z.string(), z.unknown()).describe("Permission configuration to update"),
      },
      async ({ user_id, permissions }) => {
        try {
          const data = await client.patch(`/users/${user_id}/permissions`, permissions);
          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, implying mutation, but fails to mention critical aspects like required authentication, potential side effects, error conditions, or what the response looks like, leaving significant gaps for an agent.

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 no wasted words, making it easy to parse and understand quickly. It is appropriately sized for the tool's complexity.

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?

Given this is a mutation tool with no annotations and no output schema, the description is insufficient. It lacks details on behavioral traits, error handling, and output format, which are essential for safe and effective tool invocation by an agent.

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 ('user_id' and 'permissions'). The description adds no additional meaning beyond implying the permissions object relates to Crafty and server settings, but this is minimal value over the schema's documentation.

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 ('user's Crafty and per-server permissions'), making the purpose evident. However, it doesn't distinguish this tool from its sibling 'user_update', which might handle general user updates, leaving some ambiguity about scope differentiation.

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 on when to use this tool versus alternatives like 'user_update' or 'role_update'. The description lacks context about prerequisites, such as needing user identification or specific permissions, which is critical for a mutation tool.

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