xendit-mcp

xendit_get_disbursement

Check disbursement status on Xendit to monitor refund and payout progress. Enter a disbursement ID to retrieve current transaction details.

Instructions

Get disbursement status by Xendit disbursement ID. Use for refund/payout status lookups.

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": {
      "disbursementId": "<disbursementId>"
    },
    "name": "xendit_get_disbursement"
  }
}

Input Schema

Name	Required	Description	Default
`disbursementId`	Yes	Xendit disbursement ID

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Apr 18, 2026

TDQS

A3.7/5.0

Behavior2/5

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

No annotations are provided, so the description carries the full burden. It mentions the tool is for 'status lookups' (implying read-only), but does not disclose behavioral traits such as authentication needs, rate limits, error handling, or response format. For a tool with no annotation coverage, this leaves significant gaps.

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 two concise sentences with zero waste, front-loaded with the core purpose. Every word earns its place, making it easy to parse quickly.

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?

Given no annotations and no output schema, the description is minimal but covers the basic purpose and usage. However, for a tool that likely returns status data (implied by 'status lookups'), more detail on response structure or error cases would improve completeness, leaving it at an adequate but not fully helpful level.

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 the schema fully documents the 'disbursementId' parameter. The description adds no additional meaning beyond what the schema provides (e.g., format examples or constraints), meeting the baseline for high schema coverage.

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

Purpose5/5

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

The description clearly states the specific action ('Get disbursement status') and resource ('by Xendit disbursement ID'), distinguishing it from siblings like 'xendit_get_disbursement_by_external_id' which uses a different identifier. The mention of 'refund/payout status lookups' further clarifies the use case.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides clear context for when to use this tool ('for refund/payout status lookups'), but does not explicitly state when not to use it or name alternatives like 'xendit_get_disbursement_by_external_id' for external ID lookups. The guidance is helpful but lacks explicit exclusions.

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

Deploy Server