Skip to main content
Glama
ohneben

ohneben's Wafeq MCP

wafeq_debit_notes_create

Create a debit note to bill a customer for an amount due, including contact, currency, line items, and optional notes. Use an idempotency key to avoid duplicate records.

Instructions

๐ŸŸก WRITE ยท creates data ยท Debit Notes ยท POST /debit-notes/

Create debit note

Endpoint for creating a new debit note.

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
bodyYesAdds nested create feature
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.8/5.0
Behavior4/5

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

Annotations already flag write and non-idempotent behavior, and the description reinforces this by stating 'Not idempotent โ€” calling twice creates two records.' It adds explicit guidance on idempotency_key behavior, which is valuable beyond the annotations. No contradiction.

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 short and front-loaded with the write indicator, endpoint, and non-idempotency warning. It wastes minimal space and communicates key information efficiently.

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 create tool with no output schema, the description covers the core action, endpoint, and idempotency. However, it doesn't mention required fields beyond what the schema states, and doesn't clarify the distinction between debit notes and credit notes, which could confuse an agent selecting among siblings.

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 all parameters. The description adds little about parameter semantics, but the schema itself thoroughly covers each field. The description mentions idempotency_key behavior, which supplements the schema, but otherwise does not go beyond it.

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

Purpose4/5

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

The description clearly states the tool creates a debit note via POST /debit-notes/, with a specific verb and resource. It doesn't explicitly distinguish from sibling tools like wafeq_credit_notes_create, but the resource name and endpoint make the purpose clear.

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 description identifies the endpoint and notes non-idempotency, guiding the agent to use idempotency_key for safe retries. It doesn't explicitly compare against alternatives, but the context of creating vs updating/retrieving debit notes is implied by the endpoint and resource.

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