list_conversionsRetrieve recent bank statement conversion jobs to view status, file name, and page count; optionally filter by status or limit results.
List the BankConv account's recent conversions with their status, file name and page count.
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | ||
| status | No |
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds useful context about returned fields (status, file name, page count) but says nothing about pagination, ordering, or how filtering behaves, which a listing tool should disclose.
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; the core purpose and returned fields come first. Nothing extraneous, though there is also very little content to structure.
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?
There is no output schema, so the description rightly sketches the return values, and annotations cover safety. However, for a two-parameter listing tool it omits all parameter semantics and any pagination/filtering behavior, leaving real gaps an agent must guess at.
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 0% and neither parameter (limit, status) is explained in the description. The word 'recent' loosely implies a recency-ordered default, but the limit bound, its default of 15, and the status enum values are left entirely undcoumented, so the description fails to compensate for the coverage gap.
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?
States a clear verb+resource ('List ... recent conversions') and names the fields returned (status, file name, page count). The resource is distinguishable from siblings like get_transactions and convert_statement, though the description never explicitly contrasts itself with them.
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?
Provides no when-to-use guidance, no exclusions, and no mention of alternatives such as get_transactions or download_statement. Usage is only weakly implied by the word 'recent', leaving the agent to infer when this tool is the right choice.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.