List test-case priorities and their IDs to identify available priority levels. Use optional filters to narrow results by name or product.
List test-case priorities and their ids.
| Name | Required | Description | Default |
|---|---|---|---|
| query | No | Kiwi ORM filter dict, e.g. {"name": "My Product"} or {"product_id": 3}. Omit or pass {} to list everything. |
Changes observed during successful MCP inspections.
v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations are absent, so the description carries the full burden of behavioral disclosure. 'List' implies a read-only call, but it does not state whether all priorities are returned by default, what the response shape is, or any permissions or side effects. The schema covers the omit-query behavior, but the description adds little beyond the basic action.
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?
A single front-loaded sentence with no filler; every word contributes to identifying the resource and the return value. It is concise without being incomplete to the point of tautology.
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 low-complexity read-only list with one optional parameter and full schema coverage, the description is minimally viable. However, with no annotations and no output schema, the lack of explicit usage guidance and output structure beyond 'ids' leaves noticeable gaps.
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 100%, with a clear explanation of the Kiwi ORM filter dict and explicit guidance to omit or pass {} to list everything. The description adds no parameter detail, but with full schema coverage the baseline of 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?
The description states a concrete action ('List') and a specific resource ('test-case priorities'), plus the return focus ('and their ids'). It is not a tautology and is clearly distinct from sibling get_* tools, none of which target priorities.
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 is given on when to use this tool versus alternatives like kiwi_get_categories or kiwi_get_case_statuses. The optional query behavior is documented in the schema, but the description itself provides no selection criteria, exclusions, or context for choosing it.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.