List all currencies configured in inFlow Inventory to view available options for orders, invoices, and financial records. Supports sorting, pagination, and optional total count.
List all currencies configured in inFlow
| Name | Required | Description | Default |
|---|---|---|---|
| skip | No | ||
| sort | No | Property to sort by (e.g., name, code) | |
| count | No | ||
| sortDesc | No | Sort in descending order | |
| includeCount | No | Include total record count in response |
Changes observed during successful MCP inspections.
v1.4.0-alpha.2Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the full behavioral burden, yet it only implies a read operation. It does not disclose pagination behavior, default sort order, return format, or other traits relevant to a 5-parameter list endpoint.
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 zero wasted words. It is appropriately sized for the purpose statement it provides.
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 simple read-only list tool, the description establishes the core purpose and domain. However, with no output schema and no annotations, it omits enough about pagination, sorting, and return content that an agent may need to inspect the schema to use it confidently.
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?
The description adds no meaning for any of the five optional parameters. With only 60% schema description coverage, undocumented parameters like 'skip' and 'count' receive no explanation from the description.
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 specific verb ('List') and resource ('currencies') and adds scope ('configured in inFlow'). No sibling tool covers currencies, so it is unmistakable which resource this acts on.
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?
It gives no guidance about when to use this tool versus alternatives, nor any conditions or exclusions. The intended use is obvious from 'List', but the description itself provides no routing help.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.