Skip to main content
Glama

ifthenpay Payments MCP

by com.ifthenpay

cofidis_create_payment

Creates a Cofidis Pay instalment payment. Returns a payment URL where the customer can complete the purchase in instalments.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
amountYesPayment amount in EUR. Cofidis has minimum and maximum limits per customer.
order_idYesUnique order identifier in your system (max 15 characters).
return_urlYesURL to redirect the customer after the payment flow. The API appends &Success=True on approval, or another value on failure.
cofidis_keyYesifthenpay Cofidis Pay key.
descriptionNoShort description or reference for the payment (e.g. order number).
customer_nameNoFull name of the customer.
customer_emailNoEmail address of the customer.
customer_phoneNoCustomer phone number including country code (e.g. +351256245560).

TDQS

C2.9/5.0
Behavior2/5

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

No annotations; description only says it creates a payment and returns a URL. Lacks details on side effects (e.g., immediate charge or reservation), idempotency, error scenarios, or permissions needed.

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?

Two concise, front-loaded sentences with no redundancy. Could add more detail without losing conciseness.

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?

Despite 100% schema coverage, description does not explain payment flow outcomes, error handling, or the structure of the returned URL. Incomplete for a payment creation tool with 8 parameters and no output schema.

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 already describes all 8 parameters thoroughly (100% coverage). Description adds no extra meaning beyond what schema provides, hence baseline 3.

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?

Description clearly states it creates a Cofidis Pay instalment payment and returns a payment URL. Differentiates from sibling tools via name and 'instalment' context, but could explicitly contrast with other payment creation tools.

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 on when to use this tool vs alternatives like creditcard_create_payment or pinpay_create_payment. Does not mention prerequisites (e.g., having a Cofidis key) or expected flow.

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

All ifthenpay Payments MCP toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.9/5.0
Disambiguation5/5

Each tool targets a distinct payment method or action (e.g., cofidis_create_payment vs mbway_request_payment), and the two MB WAY tools are clearly complementary (request vs check status). No ambiguity between tools.

Naming Consistency5/5

All tool names follow a consistent `method_action` pattern in snake_case (e.g., creditcard_create_payment, mbway_check_status, payments_list). Actions like `create_payment`, `create_reference`, and `request_payment` are appropriate for their respective methods.

Tool Count5/5

9 tools is well-scoped for a payment gateway MCP server, covering multiple payment methods and a list endpoint. Each tool serves a clear purpose without redundancy.

Completeness4/5

Covers creation for all payment methods and includes a status check for MB WAY. However, dedicated status/retrieve tools for other payment methods are missing; they rely on the payments_list endpoint. Missing cancellation or refund tools, which are common in payment systems.

Resources