Skip to main content
Glama
ohneben

ohneben's Wafeq MCP

wafeq_invoices_list

Read-onlyIdempotent

Retrieve invoices from Wafeq with optional filters for status, contact, project, branch, date, and time ranges, supporting pagination.

Instructions

๐ŸŸข READ-ONLY ยท Invoices ยท GET /invoices/

List invoices

Endpoint for retrieving a list of invoices.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNoA page number within the paginated result set.
branchNoThe unique identifier of the branch.
statusNoThe status of the invoice
contactNoThe unique identifier of the contact.
projectNoThe unique identifier of the project.
page_sizeNoNumber of results to return per page.
external_idNoExternal identifier
invoice_dateNoThe date of the document
created_ts_afterNoThe timestamp in UTC when the invoice was created
created_ts_beforeNoThe timestamp in UTC when the invoice was created
modified_ts_afterNoThe timestamp in UTC when the invoice was last modified
modified_ts_beforeNoThe timestamp in UTC when the invoice was last modified

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. First observedv2.0.0

TDQS

B3.1/5.0
Behavior2/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint, so the description adds no new behavioral information beyond repeating 'READ-ONLY' and 'List invoices.' It does not mention pagination behavior, filtering semantics, or any operational caveats.

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, but 'List invoices' and 'Endpoint for retrieving a list of invoices' are redundant restatements. It could be condensed to a single informative sentence without losing meaning.

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 list endpoint with no required parameters and fully documented filter parameters, the description is minimally functional. However, with no output schema, it does not explain pagination details, return shape, or how to navigate multi-page results, and it offers no differentiation within the large sibling group.

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%, with all 12 parameters already documented in the input schema. The description itself adds no parameter-level meaning, matching the baseline of 3.

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 'List invoices' and identifies the endpoint 'GET /invoices/', naming both the verb and resource. This clearly distinguishes the tool from invoice retrieve/update/create/destroy siblings.

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?

No guidance is provided about when to use this tool versus alternatives such as wafeq_invoices_retrieve, wafeq_invoices_line_items_list, or wafeq_simplified_invoices_list. There are no context cues, exclusions, or selection criteria.

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