Skip to main content
Glama
Sign In
ohneben's Wafeq MCP

ohneben's Wafeq MCP

by ohneben
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

wafeq_contacts_list

Read-onlyIdempotent

Retrieve a paginated list of contacts from Wafeq. Filter by country, keyword, or modification date to find the records you need.

Instructions

🟢 READ-ONLY · Contacts · GET /contacts/

List contacts

Endpoint for retrieving a list of contacts.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "wafeq_contacts_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoA page number within the paginated result set.
countryNo
keywordNoA search term.
page_sizeNoNumber of results to return per page.
external_idNoExternal identifier
relationshipNoMultiple values may be separated by commas.
created_ts_afterNoThe timestamp in UTC when the bill was created
created_ts_beforeNoThe timestamp in UTC when the bill was created
modified_ts_afterNoThe timestamp in UTC when the bill was last modified
modified_ts_beforeNoThe timestamp in UTC when the bill was last modified

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

C2.8/5.0
Behavior2/5

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

The annotations already declare readOnlyHint, idempotentHint, and destructiveHint false, so the description's 'READ-ONLY' adds no new behavioral information. It also does not disclose pagination behavior, filtering semantics, default page size, or what data is returned. There is no contradiction, but the description adds little beyond the 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, but it is redundant: 'List contacts' and 'Endpoint for retrieving a list of contacts' say the same thing. The emoji and endpoint line add some context, but the duplicate phrasing means 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?

With 10 parameters, no output schema, and no explanation of pagination or filtering behavior, this description is too minimal for an agent to fully understand the tool's behavior. The schema supplies parameter names, but the description misses guidance about result shape, default behavior, or how the filters interact.

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 90%, and most parameters have their own descriptions, so the baseline is 3. The tool description itself contributes nothing about parameters, but the schema carries the burden. Some schema descriptions are inaccurate or repetitive, such as the date filters referring to 'bill' rather than 'contact,' and the description does not help resolve that.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the operation: 'List contacts' and 'Endpoint for retrieving a list of contacts.' It identifies the resource and distinguishes itself from the sibling contact tools like wafeq_contacts_retrieve, create, update, and destroy. It could be stronger by noting list-specific scope or contrast, but it is unambiguous.

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?

There is no guidance about when to use this tool versus alternatives. Among the many list endpoints in the sibling set, the description does not explain that this is for contact retrieval or mention any prerequisites, exclusions, or related tools. The intended usage must be inferred entirely from the tool name.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools