Skip to main content
Glama
ohneben

ohneben's Wafeq MCP

wafeq_employees_create

Create a new employee record in Wafeq by providing name, contact, and hiring details. Use an idempotency key to prevent duplicate entries on retry.

Instructions

๐ŸŸก WRITE ยท creates data ยท Employees ยท POST /employees/

Create employee

Endpoint for creating a new employee.

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

A3.9/5.0
Behavior4/5

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

The description adds meaningful behavioral detail beyond annotations: it explains that calling twice creates two records and that the idempotency_key makes retries safe. This goes beyond the boolean idempotentHint=false and is genuinely useful for an agent.

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 opening badge and endpoint line are efficient, and the idempotency note is high-value. However, 'Create employee' and 'Endpoint for creating a new employee' are redundant, so the description is not maximally tight.

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 and no output schema, the description covers key invocation context: the endpoint, the create semantics, and the non-idempotent behavior. Combined with the detailed schema, this is sufficient for an agent to call the tool correctly, though response/return behavior is not mentioned.

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 the required body and fields. The description emphasizes idempotency_key, but the schema provides the richer detail about automatic UUID generation and header usage, so the prose adds little new semantic value.

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 clearly states the operation: it creates data for the Employees resource, and provides the exact endpoint POST /employees/. 'Create employee' unambiguously distinguishes it from sibling retrieve/update/destroy tools.

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 that this tool is used when creating a new employee, but it does not explicitly compare against alternatives like wafeq_employees_update or wafeq_employees_retrieve, nor does it 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