Skip to main content
Glama
ohneben

ohneben's Wafeq MCP

wafeq_payslips_create

Create a new payslip with employee, pay items, currency, and date. Use it to record and post employee wages in Wafeq.

Instructions

๐ŸŸก WRITE ยท creates data ยท Payslips ยท POST /payslips/

Create payslip

Endpoint for creating a new payslip.

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

A4.2/5.0
Behavior4/5

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

Annotations already mark the operation as non-idempotent, and the description goes further by explaining the consequence ('calling twice creates two records') and how idempotency_key makes retries safe. This adds useful operational context beyond the structured annotations.

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

Conciseness3/5

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

The description is short and front-loaded with a write indicator and endpoint, but it repeats the same idea three times: '๐ŸŸก WRITE ยท creates data ยท Payslips', 'Create payslip', and 'Endpoint for creating a new payslip'. The idempotency warning earns its place; the redundant 'Endpoint for...' sentence does not.

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 schema thoroughly documents the nested body and its required fields, and the description adds the essential non-idempotency and retry-safety context. The lack of any description of the return payload is a minor gap given there is no output schema, but it does not prevent correct invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is met. The description adds meaningful semantics for idempotency_key by explaining the X-Wafeq-Idempotency-Key header, automatic UUID v4 generation, and retry safety. Body parameters are left to the schema, which is appropriate given their thorough 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 names a specific verb and resource ('Create payslip', 'POST /payslips/') and clearly identifies the operation as creating a new payslip. This is immediately distinguishable from sibling retrieve, update, destroy, and partial_update operations.

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 clearly establishes that this endpoint is for creating a new payslip, giving an agent enough context to select it over the many payslip-related siblings. It does not explicitly list when-not-to-use alternatives, but the create-vs-modify distinction is implicit and unambiguous.

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