Skip to main content
Glama

user_get_permissions

Retrieve user permissions for Crafty controller and individual servers by providing a user ID.

Instructions

Get a user's Crafty and per-server permissions

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
user_idYesUser ID or '@me'

Implementation Reference

  • The implementation and registration of the user_get_permissions tool.
    server.tool(
      "user_get_permissions",
      "Get a user's Crafty and per-server permissions",
      { user_id: z.string().describe("User ID or '@me'") },
      async ({ user_id }) => {
        try {
          const data = await client.get(`/users/${user_id}/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 a 'Get' operation (implying read-only), but doesn't mention authentication requirements, rate limits, error conditions, or what the output contains (e.g., format, structure). For a tool that retrieves sensitive permission data, this lack of behavioral context is a significant gap.

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 directly states the tool's purpose without unnecessary words. It's front-loaded with the core action and target, making it easy to parse quickly.

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 tool that retrieves permission data (potentially complex and sensitive), the description is inadequate. There's no output schema, and the description doesn't explain what the return values include (e.g., Crafty permissions vs. server-specific permissions, format). With no annotations and incomplete behavioral context, this leaves significant gaps for an agent to understand how to use the tool effectively.

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 'user_id' fully documented in the schema as 'User ID or '@me''. The description doesn't add any additional meaning beyond this, such as explaining what '@me' refers to or providing examples. Given the high schema coverage, the baseline score of 3 is appropriate.

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 ('Get') and the target ('user's Crafty and per-server permissions'), making the purpose immediately understandable. It doesn't explicitly differentiate from sibling tools like 'user_get' or 'user_get_api_keys', but the specificity about permissions provides reasonable distinction.

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_get' (which might return basic user info) or 'user_update_permissions' (for modifying permissions). The description implies it's for retrieving permission data but offers no context about prerequisites, timing, or comparisons to sibling tools.

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