Mintline MCP Server

list_statements

Retrieve a paginated list of uploaded bank statements. Use limit and offset parameters to control the page size and starting position.

Instructions

List statements. Retrieve a list of uploaded bank statements.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "limit": "<limit>",
      "offset": "<offset>"
    },
    "name": "list_statements"
  }
}

Input Schema

Name	Required	Description	Default
`limit`	Yes	Items per page
`offset`	Yes	Pagination offset

Schema Changelog

Changes observed during successful MCP inspections.

Changed5 schema fields changedv1.1.9May 6, 2026

addedInput schema / properties / limit / default
```
Added value: +50
```

changedInput schema / properties / limit / description

Previous value: -"Max results to return (default 20)"New value: +"Items per page"

changedInput schema / properties / limit / type

Previous value: -"number"New value: +"integer"

addedInput schema / properties / offset

Added value: +{
+  "default": 0,
+  "description": "Pagination offset",
+  "type": "integer"
+}

addedInput schema / required

Added value: +[
+  "limit",
+  "offset"
+]

First observedv1.1.0Feb 1, 2026

TDQS

B3.2/5.0

Behavior2/5

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

No annotations are provided, so the description must disclose all behavioral traits. It does not mention pagination, rate limits, data ordering, or any side effects. Only the basic listing action is stated.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is very short with two sentences, front-loading the purpose. However, it could be slightly redundant ('List statements' then 'Retrieve a list...'). Still, it is efficient.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple list tool with two parameters and no output schema, the description is minimally adequate but lacks details on return format, ordering, or pagination behavior. The parameters hint at pagination but are not explained.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100% with clear descriptions for 'limit' and 'offset'. The description does not add any additional meaning beyond the schema, so baseline 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the verb 'list' and the resource 'statements' with the phrase 'list of uploaded bank statements'. It is specific and distinguishes from sibling tools like 'get_statement' (single item) and 'list_receipts' (different resource).

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance on when to use this tool versus alternatives such as 'list_exports' or 'list_receipts'. The description does not mention any prerequisites, exclusions, or context for usage.

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