whmcs_get_serversRetrieve the list of configured WHMCS servers, with an option to fetch status. Use this to verify server inventory and check operational health.
Get list of configured servers
| Name | Required | Description | Default |
|---|---|---|---|
| fetchStatus | No | Fetch server status |
Changes observed during successful MCP inspections.
v1.2.1Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations provided, yet description only states purpose without disclosing any behavioral traits (e.g., idempotency, performance, authentication). With no annotations, the description carries the burden but provides minimal insight.
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?
Single sentence is concise and front-loaded. No unnecessary words; earns its place.
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?
No output schema, yet description does not mention return format or behavior. For a list tool, it could be more complete, especially given the rich sibling context (many tools have more detailed descriptions).
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 boolean parameter 'fetchStatus' described as 'Fetch server status'. Description adds no further meaning beyond what the schema already provides, so baseline 3 is appropriate.
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?
Description clearly states 'Get list of configured servers' with specific verb and resource. Distinguishable from many get_* siblings because it targets servers specifically.
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 explicit when-to-use or alternatives guidance, but for a simple list retrieval tool the context is implied. Basic usage is clear.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.