tabby-mcp

get_payment

Retrieve detailed information about a specific payment using its unique ID. Enables viewing payment status and details within the Tabby BNPL platform.

Instructions

Get payment details by ID.

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": {
      "payment_id": "<payment_id>"
    },
    "name": "get_payment"
  }
}

Input Schema

Name	Required	Description	Default
`payment_id`	Yes	Payment ID

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0May 28, 2026

TDQS

B3.1/5.0

Behavior2/5

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

The description does not disclose any behavioral traits such as read-only nature, idempotency, authentication requirements, or error behavior. Since no annotations are provided, the description carries the full burden, and it fails to go beyond stating the basic operation.

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 sentence with no redundant words. It efficiently conveys the core purpose without any filler.

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 simple get-by-ID tool with one parameter and no output schema, the description is adequate but minimal. It does not cover return format, error cases, or any additional behavior. Given the simplicity, a score of 3 is reasonable.

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 coverage is 100% for the single parameter, so the baseline is 3. The description adds no additional meaning beyond what the schema provides (both say 'by ID' and 'Payment ID'). No format or constraints are elaborated.

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 tool retrieves payment details by ID. It uses a specific verb 'Get' and resource 'payment details', which is unambiguous. However, it does not explicitly differentiate from sibling tools like list_payments or get_session, which slightly reduces the score from a perfect 5.

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 on when to use this tool versus alternatives. The description implies usage when a payment ID is known, but there is no explicit context or exclusions (e.g., 'use get_payment when you have a specific ID, use list_payments to browse').

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

Deploy Server