Skip to main content
Glama

user_get

Retrieve user details from Crafty Controller, including current authenticated user information when using '@me' as the user identifier.

Instructions

Get details for a specific Crafty Controller user. Use '@me' as user_id to get the currently authenticated user.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
user_idYesUser ID or '@me' for the current user

Implementation Reference

  • Implementation of the user_get MCP tool, which fetches user details from the Crafty Controller.
    server.tool(
      "user_get",
      "Get details for a specific Crafty Controller user. Use '@me' as user_id to get the currently authenticated user.",
      { user_id: z.string().describe("User ID or '@me' for the current user") },
      async ({ user_id }) => {
        try {
          const data = await client.get(`/users/${user_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 };
        }
      }
    );
Behavior3/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 clearly indicates this is a read operation ('Get details'), but doesn't mention authentication requirements, rate limits, error conditions, or what specific details are returned. It provides basic context about the '@me' special case but lacks comprehensive behavioral information.

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?

Two sentences with zero waste. The first sentence states the core purpose, and the second provides crucial usage guidance about the '@me' special case. Every word earns its place, and the information is front-loaded appropriately.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a single-parameter read tool with no annotations and no output schema, the description is adequate but has clear gaps. It explains what the tool does and provides the '@me' special case, but doesn't describe what user details are returned, authentication requirements, or potential error scenarios. The description is minimally viable but could be more complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/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 fully documents the single parameter. The description adds valuable semantic context by explaining the special meaning of '@me' as a value for user_id, which goes beyond the schema's description. This additional meaning is helpful for correct tool invocation.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the specific action ('Get details') and resource ('Crafty Controller user'), and distinguishes itself from siblings like user_list (which lists users) and user_get_permissions (which gets permissions). It provides a precise verb+resource combination with clear scope.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides clear context on when to use this tool ('to get details for a specific user') and includes the special case '@me' for the current authenticated user. However, it doesn't explicitly mention when not to use it or name specific alternatives like user_list for listing all users.

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