Bankstatemently

Rate Statement Conversion

rate_statement

Destructive

Report how well a previously converted bank statement was parsed: submit a 1-5 rating, optionally with structured feedback at any rating. Your rating counts toward the average ratings shown on bankstatemently.com. Calling this again for the same document updates your existing rating without clearing feedback already submitted for it. Returns the stored rating state in the response — there is no separate tool to read your own rating back. Every response includes a "summary" field: use it as the single source of truth for what happened.

Input Schema

TableJSON Schema

Name	Required	Description
`rating`	Yes	1-5 star rating for this conversion
`feedback`	No	Free-text feedback.
`document_id`	Yes	Document ID (from convert_statement or list_statements)
`feedback_categories`	No	Structured feedback categories.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`hint`	No
`error`	No
`rating`	No
`status`	Yes
`message`	No
`summary`	No
`documentId`	No
`hasFeedback`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 6, 2026

changedInput schema / properties / feedback / description

Previous value: -"Free-text feedback. Only when the rating is 3 or below."New value: +"Free-text feedback."

changedInput schema / properties / feedback_categories / description

Previous value: -"Structured feedback categories. Only when the rating is 3 or below."New value: +"Structured feedback categories."

Changed2 schema fields changedOct 4, 2026

changedInput schema / properties / feedback / description

Previous value: -"Free-text feedback. Only accepted when rating is 3 or below."New value: +"Free-text feedback. Only when the rating is 3 or below."

changedInput schema / properties / feedback_categories / description

Previous value: -"Structured feedback categories. Only accepted when rating is 3 or below."New value: +"Structured feedback categories. Only when the rating is 3 or below."

Changed5 schema fields changedOct 4, 2026

removedInput schema / properties / export_format

Removed value: -{
-  "description": "Which output format you exported this conversion to (csv, xlsx, qbo, or xero).",
-  "enum": [
-    "csv",
-    "xlsx",
-    "qbo",
-    "xero"
-  ],
-  "type": "string"
-}

removedInput schema / properties / use_case

Removed value: -{
-  "description": "Tags describing what you use the converted data for.",
-  "items": {
-    "enum": [
-      "bookkeeping",
-      "tax_preparation",
-      "financial_analysis",
-      "audit_compliance",
-      "reconciliation",
-      "personal_finance",
-      "data_migration",
-      "other"
-    ],
-    "type": "string"
-  },
-  "type": "array"
-}

removedInput schema / properties / use_case_other

Removed value: -{
-  "description": "Free-text use case, for when \"other\" is among the use_case tags.",
-  "maxLength": 500,
-  "type": "string"
-}

removedOutput schema / properties / useCase

Removed value: -{
-  "items": {
-    "type": "string"
-  },
-  "type": "array"
-}

removedOutput schema / properties / useCaseOther

Removed value: -{
-  "anyOf": [
-    {
-      "type": "string"
-    },
-    {
-      "type": "null"
-    }
-  ]
-}

Changed9 schema fields changedSep 4, 2026

changedInput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

addedInput schema / properties / document_id / description

Added value: +"Document ID (from convert_statement or list_statements)"

addedInput schema / properties / export_format / description

Added value: +"Which output format you exported this conversion to (csv, xlsx, qbo, or xero)."

addedInput schema / properties / feedback / description

Added value: +"Free-text feedback. Only accepted when rating is 3 or below."

addedInput schema / properties / feedback_categories / description

Added value: +"Structured feedback categories. Only accepted when rating is 3 or below."

addedInput schema / properties / rating / description

Added value: +"1-5 star rating for this conversion"

addedInput schema / properties / use_case / description

Added value: +"Tags describing what you use the converted data for."

addedInput schema / properties / use_case_other / description

Added value: +"Free-text use case, for when \"other\" is among the use_case tags."

changedOutput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

Changed7 schema fields changedAug 21, 2026

removedInput schema / properties / document_id / description

Removed value: -"Document ID (from convert_statement or list_statements)"

removedInput schema / properties / export_format / description

Removed value: -"Which output format you exported this conversion to (csv, xlsx, qbo, or xero)."

removedInput schema / properties / feedback / description

Removed value: -"Free-text feedback. Only accepted when rating is 3 or below."

removedInput schema / properties / feedback_categories / description

Removed value: -"Structured feedback categories. Only accepted when rating is 3 or below."

removedInput schema / properties / rating / description

Removed value: -"1-5 star rating for this conversion"

removedInput schema / properties / use_case / description

Removed value: -"Tags describing what you use the converted data for."

removedInput schema / properties / use_case_other / description

Removed value: -"Free-text use case, for when \"other\" is among the use_case tags."

First observedAug 12, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Beyond annotations (readOnlyHint=false, destructiveHint=true, openWorldHint=true), the description discloses genuinely useful traits: repeat calls upsert and do not clear prior feedback, the response returns stored rating state, and there is no separate read-your-rating tool. It also flags the response's "summary" field as authoritative. It does not mention auth/rate limits or exactly what the destructive hint entails.

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?

Purpose is front-loaded and every sentence carries information (upsert semantics, return behavior, summary field). It is slightly dense and could tighten the return-value sentence, but there is no filler.

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 an output schema present, return values need not be spelled out, and the description still points at the summary field. It covers the write/upsert semantics, guidance, and destination of the rating (site average), leaving only edge cases like permission or failure handling unspecified.

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%, so the schema already documents rating, feedback, document_id, and feedback_categories. The description adds only mild nuance (feedback is optional at any rating) that the schema's optionality already implies, so the baseline of 3 applies.

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 states a specific verb and resource: report a 1-5 rating on how well a previously converted bank statement was parsed, optionally with structured feedback. There is no sibling that overlaps this capability (the rest of the toolset covers conversion, listing, aggregation, and transfer adjudication), so the agent can identify it immediately.

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

Usage Guidelines4/5

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

It gives clear context for use (after a statement has been converted; feedback is optional at any rating) and explains the repeat-call behavior. It does not explicitly state when NOT to use it or name an alternative, so it stops short of the 5 tier.

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

All Bankstatemently tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.