Skip to main content
Glama
ohneben

ohneben's Wafeq MCP

wafeq_bank_accounts_ledger_transactions_create

Create a bank ledger transaction for a specified bank account by providing account, amount, and date. Include an idempotency key to prevent duplicate entries when retrying.

Instructions

๐ŸŸก WRITE ยท creates data ยท Bank Ledger Transactions ยท POST /bank-accounts/{bank_account_id}/ledger-transactions/

Create bank ledger transaction

Endpoint for creating a new bank ledger transaction.

Not idempotent โ€” calling twice creates two records. Pass idempotency_key (or let the server generate one) to make a retry safe.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
bodyYesA ModelSerializer that takes additional arguments for "fields", "omit" and "expand" in order to control which fields are displayed, and whether to replace simple values with complex, nested serializations
bank_account_idYes
idempotency_keyNoOptional idempotency key (sent as the X-Wafeq-Idempotency-Key header). A UUID v4 is generated automatically when omitted, so an automatic network retry can never duplicate this operation. Pass your own stable value to make a deliberate re-invocation safe as well.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. First observedv2.0.0

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already indicate a write operation and non-idempotence, but the description adds the concrete consequence that 'calling twice creates two records' and explains how idempotency_key makes retries safe. This is valuable behavioral context beyond the boolean hints.

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 compact and front-loaded with the HTTP method and endpoint. Minor redundancy exists between 'Create bank ledger transaction' and 'Endpoint for creating a new bank ledger transaction,' but the overall structure is efficient.

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?

For a write operation with a nested body schema and no output schema, the description covers the key invocation concerns: endpoint, side effects, and retry safety. The body requirements are adequately delegated to the input schema.

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 67%, and the schema already documents idempotency_key and the body fields. The description's idempotency_key guidance mostly restates the schema parameter description rather than adding new semantic meaning.

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 names the action 'creating' and the resource 'bank ledger transaction,' and front-loads the exact endpoint POST /bank-accounts/{bank_account_id}/ledger-transactions/. This clearly distinguishes it from sibling tools like statement_transactions_create.

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

Usage Guidelines3/5

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

The description implies use when creating a bank ledger transaction, and the idempotency note provides practical guidance for retries. However, it does not explicitly contrast this tool with related alternatives such as statement_transactions_create or state when not to use it.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/ohneben/Wafeq-MCP'

If you have feedback or need assistance with the MCP directory API, please join our Discord server