tabby-mcp

create_payment

Initiate a payment from an approved session by specifying amount, currency, description, and order reference.

Instructions

Create a payment from an approved session.

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": {
      "amount": "<amount>"
    },
    "name": "create_payment"
  }
}

Input Schema

Name	Required	Description	Default
`amount`	Yes	Payment amount
`currency`	No	Currency code	AED
`description`	No	Payment description
`order_reference`	No	Merchant order reference

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0May 28, 2026

TDQS

C2.9/5.0

Behavior2/5

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

With no annotations, the description carries full burden. It indicates a create/mutation action but provides no details on side effects, permissions, or outcomes. The mention of 'approved session' hints at a precondition but is insufficient.

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 description is a single sentence with no wasted words, but it is arguably too terse for a 4-parameter tool. It is front-loaded but lacks depth.

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 complexity (4 params, no output schema, no annotations), the description is incomplete. It omits details on prerequisites, return values, and error conditions, leaving gaps for the agent.

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 baseline is 3. The description adds no direct parameter guidance beyond what the schema already provides, which is adequate but not enhanced.

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 ('Create') and the resource ('payment'), with a qualifying condition ('from an approved session'). It distinguishes from siblings like 'capture' by implying a prerequisite, though not explicitly.

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 does not provide guidance on when to use this tool versus alternatives (e.g., 'capture', 'void'). It mentions a prerequisite ('approved session') but does not elaborate on when not to use it or clarify the context.

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

Deploy Server