Skip to main content
Glama
Sign In
BankConv MCP server

BankConv MCP server

by wassim
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

List recent conversions

list_conversions
Read-only

Retrieve recent BankConv conversions, newest first, to find an earlier conversion ID for downloads or check processing status.

Instructions

List the BankConv account's recent conversions, newest first, one line each: conversion id, status, file name, page count and upload time. Use it to find the id of an earlier conversion for get_transactions or download_statement, or to check on one still processing. Read-only.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_conversions"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoHow many conversions to list, 1 to 100.
statusNoOnly list conversions with this status. no_credits means it waits for pages; failed means the PDF couldn't be converted.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.1.1
    • addedInput schema / properties / limit / description
      Added value: +"How many conversions to list, 1 to 100."
    • addedInput schema / properties / status / description
      Added value: +"Only list conversions with this status. no_credits means it waits for pages; failed means the PDF couldn't be converted."
  2. First observedv0.1.0

TDQS

A4.4/5.0
Behavior4/5

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

Beyond the annotations it discloses ordering (newest first), the one-line-per-item return shape and the specific fields returned, which is real value since there is no output schema. 'Read-only' merely restates readOnlyHint and the 'recent' window is never quantified, so it falls just short of a 5.

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

Conciseness5/5

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

Two sentences, front-loaded with the verb and resource, then the use cases. Every clause carries information; nothing is redundant except the short 'Read-only' tag.

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

Completeness4/5

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

With no output schema, the description usefully spells out the returned fields and ordering, which covers the main completeness gap. Minor omissions remain: how 'recent' is bounded and what happens past the 100-item cap, though the limit parameter largely addresses the latter.

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 coverage is 100% with both parameters fully described (including the enum semantics for status), so the schema does the heavy lifting. The description does not mention limit or status filtering at all, leaving no added meaning beyond the structured fields — baseline 3.

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?

States a specific verb and resource ('List the BankConv account's recent conversions') plus sorting ('newest first') and per-item fields returned. That scope makes it clearly distinct from convert_statement, get_transactions and download_statement without needing to open any schema.

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

Usage Guidelines5/5

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

Gives two concrete use cases — find a conversion id to feed get_transactions or download_statement, or check on a still-processing conversion — and names the sibling tools it precedes. The agent knows exactly when to reach for it rather than a sibling.

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

Deploy Server

Other Tools