block_userBlock a Drupal user account by UID to restrict access and prevent further logins. Use it to suspend accounts during moderation or security incidents.
Block a user account.
| Name | Required | Description | Default |
|---|---|---|---|
| uid | Yes |
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden. It states no behavioral traits: whether the block is reversible, whether it requires permissions, what happens to active sessions, or whether it affects content authored by the user. A single tautological sentence adds nothing.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single short sentence, front-loaded and free of waste. However, it is under-specified rather than concise; brevity here comes at the cost of information.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
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, 0% parameter documentation, and a rich sibling set, the description is inadequate. Even with an output schema, the agent lacks guidance on effect, permissions, and reversibility.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 0% and the single parameter 'uid' is undocumented in both schema and description. The description doesn't identify the uid as a user identifier or its expected format, leaving the agent to infer it from the tool name.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a clear verb (Block) and resource (user account). It distinguishes itself from unblock_user by its action, though it doesn't explicitly mention that sibling. Minimal but specific enough to convey intent.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No when-to-use guidance. Given the sibling unblock_user and the user management set (create_user, delete_user, update_user), the description offers no indication of prerequisites or relationship to these alternatives.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.