Skip to main content
Glama
Sign In
nz-openbank-mcp

nz-openbank-mcp

by thatskiff33
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Report Transaction Issue

txn_report_transaction_issue

Submit a support ticket to Akahu staff about a transaction to report duplicates or enrichment errors or suggestions, with issue details and optional comment.

Instructions

Submit a support ticket about a transaction to Akahu staff.

Sends a ticket to a human at Akahu support. Always elicits user confirmation (not bypass-eligible); the prompt shows every value in the ticket, including the comment. Missing required values are collected before that prompt. issue_type validation:

  • "DUPLICATE": requires other_transaction_id (the paired duplicate).

  • "ENRICHMENT_ERROR": requires fields=[...] listing affected field names.

  • "ENRICHMENT_SUGGESTION": requires fields=[...] listing suggested fields.

Returns {"success": bool, "message": str | None}.

Input Schema

NameRequiredDescriptionDefault
fieldsNoAffected field names; required for ENRICHMENT_* issue types. Omitted -> the user is prompted to supply them via elicitation.
commentNoOptional free-text context for the support agent, up to 1,000 characters.
issue_typeYesOne of "DUPLICATE", "ENRICHMENT_ERROR", "ENRICHMENT_SUGGESTION".
transaction_idYesAkahu transaction id the ticket is about.
other_transaction_idNoPaired transaction id; required for DUPLICATE. Omitted -> the user is prompted to supply it via elicitation.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.1.6
    • changedInput schema / properties / comment / anyOf
      Previous value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "maxLength": 1000,
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]
    • changedInput schema / properties / comment / description
      Previous value: -"Optional free-text context for the support agent."New value: +"Optional free-text context for the support agent, up to\n1,000 characters."
    • addedInput schema / properties / issue_type / enum
      Added value: +[
+  "DUPLICATE",
+  "ENRICHMENT_ERROR",
+  "ENRICHMENT_SUGGESTION"
+]
  2. First observedv0.1.0

TDQS

A4.4/5.0
Behavior5/5

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

Adds substantial behavioral detail beyond annotations: it always elicits user confirmation, is not bypass-eligible, shows every ticket value including the comment, and collects missing required values before the confirmation prompt. It also discloses the return shape, while annotations already cover readOnly=false and destructive=false.

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 front-loaded and appropriately sized for a tool with conditional validation and confirmation behavior. There is minor redundancy between 'Submit a support ticket about a transaction to Akahu staff' and 'Sends a ticket to a human at Akahu support.'

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

Completeness5/5

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

Given the tool's mutation/support complexity, rich annotations, complete schema coverage, and output schema, the description is complete. It covers confirmation behavior, conditional issue_type validation, elicitation of missing values, and return shape.

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 parameter meanings and conditional requirements. The description reinforces the issue_type-to-required-field mapping, but mostly repeats what the schema already states rather than adding new syntax or format details.

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: submitting a support ticket about a transaction to Akahu staff. It clearly distinguishes this from sibling transaction retrieval tools, which only fetch transaction data.

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?

The context makes clear when to use it: reporting a transaction issue to human support. It does not explicitly name when not to use it or compare against alternatives, but sibling tools are all retrieval/account operations rather than support-reporting alternatives.

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