Skip to main content
Glama
Sign In
Satim Payment Gateway Integration

Satim Payment Gateway Integration

by zakblacki
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Hybrid

configure_credentials

Set up merchant credentials for SATIM payment gateway integration. Enter the login and password received during registration to enable secure processing of CIB/Edhahabia card payments through the SATIM-ePAY platform.

Instructions

Configure SATIM payment gateway credentials

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "userName": "<userName>",
      "password": "<password>"
    },
    "name": "configure_credentials"
  }
}

Input Schema

NameRequiredDescriptionDefault
passwordYesMerchant's password received during registration
userNameYesMerchant's login received during registration

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It implies a mutation operation ('configure'), but doesn't specify whether this is a one-time setup, if it overwrites existing credentials, requires specific permissions, or has side effects like authentication changes. This is a significant gap for a tool that likely modifies system state.

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

Conciseness5/5

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

The description is a single, efficient sentence with zero wasted words. It's front-loaded with the core action and resource, making it easy to parse quickly.

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?

Given the lack of annotations and output schema, and the tool's likely role in mutating payment credentials, the description is incomplete. It doesn't address behavioral aspects like security implications, error handling, or what success looks like, which are critical for an agent to use this tool safely and effectively.

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?

The schema description coverage is 100%, with both parameters ('userName' and 'password') clearly documented in the schema. The description adds no additional meaning beyond what the schema provides, such as format examples or validation rules, so it meets the baseline for high schema coverage.

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 action ('configure') and the resource ('SATIM payment gateway credentials'), making the purpose understandable. However, it doesn't differentiate this tool from its siblings like 'register_order' or 'validate_payment_response', which might also involve credential handling in some contexts.

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?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., needing registration first), exclusions, or how it relates to sibling tools like 'register_order', leaving the agent to guess the appropriate context.

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

Related Tools