List enabled CAPTCHA products with their final per-task prices and exact product codes. Use the returned productCode with the schema tool before creating a task.
List enabled CAPTCHA products. price is the final per-task price; do not recalculate it. Use productCode exactly as returned, and read nex_captcha_product_schema(productCode) before creating a task.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v2026.10.24Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
readOnlyHint=true is consistent with 'List', so no contradiction. Beyond annotations, it discloses two non-obvious behavioral constraints: price is already the final per-task price (do not recalculate) and productCode must be used verbatim. It doesn't discuss result size or ordering, but the safety profile is already covered by annotations.
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?
Three short sentences, zero filler, with the core purpose front-loaded and the two caveats (price, productCode) plus the required follow-up call placed after it. Every sentence carries operational 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?
No output schema exists, so describing the meaning of price and productCode is essential and is done. The pre-task workflow step is also covered. Minor gap: it never indicates what fields each product object contains or how many are returned, so an agent must still infer the response shape.
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?
Zero input parameters, so the baseline is 4 by rule. The description instead invests in output-field semantics ('price is the final per-task price', productCode format), which is relevant given there is no output schema, though it does not enumerate the full returned field set.
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?
Opens with a specific verb and resource plus scope: 'List enabled CAPTCHA products.' The word 'enabled' signals a filter, and the tool is clearly distinguishable from sibling nex_captcha_product_schema (schema lookup) and nex_captcha_buy (purchase).
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?
Gives explicit downstream routing: read nex_captcha_product_schema(productCode) before creating a task, and pass productCode 'exactly as returned'. That is real when/how guidance. It stops short of naming alternatives or exclusions, but for a zero-param catalog listing no meaningful alternatives exist.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.