Skip to main content
Glama

user_update

Modify Crafty Controller user account details by specifying user ID and fields to update, enabling account management and configuration changes.

Instructions

Update a Crafty Controller user account

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
user_idYesUser ID or '@me' for the current user
updatesYesUser fields to update

Implementation Reference

  • The "user_update" tool handler implementation, which uses the client to patch a user's account data.
    server.tool(
      "user_update",
      "Update a Crafty Controller user account",
      {
        user_id: z.string().describe("User ID or '@me' for the current user"),
        updates: z.record(z.string(), z.unknown()).describe("User fields to update"),
      },
      async ({ user_id, updates }) => {
        try {
          const data = await client.patch(`/users/${user_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?

No annotations are provided, so the description carries full burden for behavioral disclosure. It states this is an update operation, implying mutation, but doesn't disclose critical traits like required permissions, whether changes are reversible, rate limits, or what happens on success/failure. For a mutation tool with zero annotation coverage, this is a significant gap in transparency.

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 front-loads the core purpose with zero waste. Every word earns its place, making it easy to parse quickly without unnecessary elaboration.

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 incomplete. It lacks information on behavioral traits (e.g., auth needs, side effects), output format, error handling, and differentiation from siblings like user_update_permissions. For a tool that modifies user accounts, more context is needed for safe and effective use.

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 updates). The description doesn't add any meaning beyond what the schema provides—it doesn't explain what fields can be in 'updates', format constraints, or special cases like '@me'. Baseline 3 is appropriate when 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 ('Update') and resource ('Crafty Controller user account'), making the purpose immediately understandable. It distinguishes from siblings like user_create, user_delete, and user_get by specifying an update operation. However, it doesn't explicitly differentiate from user_update_permissions, which is a more specific sibling.

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. The description doesn't mention prerequisites (e.g., needing authentication), when not to use it (e.g., for permission updates), or direct alternatives like user_update_permissions for permission-specific changes. Usage context is implied but not explicit.

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