GoClaw MCP Server

goclaw_skill_grant_user

Grant user access to a specific skill by providing skill and user IDs. This tool enables administrators to manage skill permissions within the GoClaw AI gateway infrastructure.

Instructions

Grant a user access to a skill

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "skill_id": "<skill_id>",
      "user_id": "<user_id>"
    },
    "name": "goclaw_skill_grant_user"
  }
}

Input Schema

Name	Required	Description	Default
`skill_id`	Yes	Skill ID
`user_id`	Yes	User ID

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Mar 15, 2026

TDQS

C2.9/5.0

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. It states this is a 'grant' operation which implies a write/mutation, but doesn't disclose behavioral traits like required permissions, whether this is idempotent, what happens on failure, or if there are rate limits. For a mutation tool with zero annotation coverage, this is insufficient.

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, clear sentence with zero wasted words. It's perfectly front-loaded, immediately conveying the core purpose without unnecessary elaboration. Every word earns its place.

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 incomplete. It doesn't explain what 'grant access' entails (e.g., what permissions are granted), what the return value might be, or potential side effects. Given the complexity of access control operations, more context is needed for the agent to use this 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 both parameters clearly documented in the schema. The description doesn't add any additional meaning about the parameters beyond what the schema provides (skill_id and user_id). This meets the baseline expectation when schema coverage is complete.

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 ('Grant') and the resource ('access to a skill'), making the purpose immediately understandable. It distinguishes from sibling tools like 'goclaw_skill_grant_agent' by specifying 'user' rather than 'agent', but doesn't explicitly differentiate from other grant-like operations in the sibling list.

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., existing skill/user), when not to use it, or what happens after granting access. With many sibling tools available, this lack of context leaves the agent guessing about appropriate usage scenarios.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server