Skip to main content
Glama
ohneben

ohneben's Wafeq MCP

wafeq_bills_create

Create a new vendor bill with line items, due date, and currency in Wafeq. Use it to record accounts payable and supply an idempotency key to prevent duplicate records on retry.

Instructions

๐ŸŸก WRITE ยท creates data ยท Bills ยท POST /bills/

Create bill

Endpoint for creating a new bill.

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.7/5.0
Behavior5/5

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

The annotations already mark this as non-read-only and non-idempotent, and the description adds concrete behavioral context: calling twice creates two records, and passing an idempotency_key or letting the server generate one makes retries safe. This meaningfully helps an agent understand the write semantics and avoid accidental duplication.

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 a clear write label, endpoint, and the most important behavioral caveat. However, 'Create bill' and 'Endpoint for creating a new bill' are redundant, so not every sentence earns its place.

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

Completeness2/5

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

This is a complex create operation with a large nested body schema and no output schema, yet the description does not mention what the API returns (e.g., created bill ID or object) or any prerequisites such as referenced contacts/accounts needing to exist. The idempotency note is useful, but the description remains incomplete for safe invocation of a complex write tool.

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 baseline is 3. The tool description's idempotency_key note largely restates what the schema already explains, and it adds no new parameter-level meaning beyond the schema's detailed descriptions.

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 explicitly states a specific verb ('creates'), resource ('Bills'), and endpoint ('POST /bills/'), making it unmistakable that this tool creates new bills. It also reinforces the create semantics by warning that calling twice creates two records, which clearly distinguishes it from read/update/delete bill operations.

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

Usage Guidelines2/5

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

The description gives no explicit guidance on when to use this tool versus alternatives such as wafeq_bills_update, wafeq_bills_partial_update, or wafeq_purchase_orders_bill_create. Usage is only implied by the verb 'create', with no mention of when not to use it or what differentiates it from related bill operations.

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