Skip to main content
Glama
ohneben

ohneben's Wafeq MCP

wafeq_accounts_create

Create a new account in the Wafeq chart of accounts by providing an account code, classification, and payment settings. Use an idempotency key to make retries safe.

Instructions

๐ŸŸก WRITE ยท creates data ยท Accounts ยท POST /accounts/

Create account

Endpoint for creating a new account.

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
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

A4/5.0
Behavior4/5

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

Beyond the annotations (readOnlyHint=false, idempotentHint=false), the description adds a valuable warning: 'Not idempotent โ€” calling twice creates two records' and explains how to use idempotency_key for safe retries. This gives actionable behavioral context that is not present in the annotations alone.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is extremely concise and well-structured. The header line conveys key metadata (write operation, resource, endpoint) at a glance, followed by a one-sentence purpose and a focused non-idempotency caveat. No unnecessary words exist.

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?

The tool is a straightforward create operation with a nested body; all required field semantics are fully documented in the schema. The description covers the critical behavioral edge case (non-idempotency). The absence of an output schema means a small gap regarding the response format, but this is minor given that the created account can be retrieved via sibling tools.

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?

The input schema covers 100% of parameters with detailed descriptions, so the baseline is 3. The description adds a practical note about idempotency_key for retry safety, but does not elaborate on body fields beyond what the schema already provides. This is a modest increment over the baseline.

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 'Create account' and 'Endpoint for creating a new account', with a clear verb and resource. The structured header 'POST /accounts/' and 'creates data' differentiate this from sibling operations like update, retrieve, or destroy.

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 provides clear context that this tool is for creating a new account, which implies its primary use case. However, it does not explicitly mention alternatives like update or destroy, nor does it include exclusions or prerequisites. The usage is inferred from the purpose rather than explicitly guided.

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