WAzion MCP Server

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description carries the full burden. It fails to disclose pagination behavior (despite having 'page' and 'limit' parameters), whether results are ordered chronologically, rate limits, or what data structure is returned. The '[query]' artifact at the end appears to be a placeholder error.

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 brief (three fragments), but the opening 'Ver conversaciones del plugin' tautologically restates the tool name. The '[query]' fragment at the end appears to be a copy/paste artifact or unfilled parameter reference that should have been removed, detracting from clarity.

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 read-only listing tool with no output schema, the description covers the basic functionality and filtering capability. However, it lacks important context such as default sorting order, maximum pagination limits, or the distinction between using 'period' versus explicit date ranges. Given the many sibling conversation tools, more differentiation would improve completeness.

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?

With 100% schema description coverage, the baseline is 3. The description adds context by mentioning time period filtering ('Soporta filtros por periodo de tiempo'), which corresponds to the 'period', 'date_from', and 'date_to' parameters. However, it does not mention the pagination parameters ('limit', 'page') or provide usage guidance on combining date filters with pagination.

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 clearly states it retrieves/displays web chat plugin conversations ('Muestra las conversaciones del plugin de chat web') and mentions time period filtering capability. However, it does not distinguish from the sibling tool 'get_plugin_conversation_detail' (single vs. list view), which is important given the similar naming.

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 provided on when to use this versus alternatives like 'get_plugin_conversation_detail', 'get_plugin_chat_sessions', or 'search_conversations'. The only usage hint is that it 'supports time period filters', which describes capability rather than selection criteria.

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