hcloud_list_users
List IAM users in your Huawei Cloud account. Provide an optional limit to control the number of results returned.
Instructions
List IAM users
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | Max results |
List IAM users in your Huawei Cloud account. Provide an optional limit to control the number of results returned.
List IAM users
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | Max results |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations provided; the description does not disclose any behavioral traits such as pagination, default behavior, authentication needs, or rate limits.
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 extremely short (3 words) but lacks necessary details, making it under-specified rather than appropriately concise.
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?
Given the simplicity, the description fails to mention return format, pagination, or any post-usage behavior; it is incomplete for practical use.
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 coverage is 100% with one parameter described as 'Max results'; the description adds no additional meaning beyond the schema, so baseline score applies.
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?
The description 'List IAM users' clearly states the action (list) and the resource (IAM users), differentiating it from other list tools for different resource types.
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 guidance on when to use this tool vs alternatives like hcloud_list_user_policies or other list tools; no mention of prerequisites or context.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/juandvasquezp/hcloud-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server