Skip to main content
Glama
georgi-shulev

Yugo MCP Server

create_payin

Create a payin to accept funds from a payer, specifying amount, payer details, and return URL for redirect after payment.

Instructions

Create Payin — Create a new Payin resource - accepting funds from a Payer — [POST /payins]

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
payerYesInformation about the Payer. If providing name information, both `first_name` and `last_name` must be provided together.
amountYesAmount the Payer will be charged
paymentNo
referenceNoMerchant-defined reference identifier for this Payin
return_urlYesURL where the Payer will be redirected after completing or canceling the Payin
settlementNo
webhook_urlNoURL where Yugo will send webhook notifications for Payin status changes
idempotency_keyNoOptional idempotency key for safe retries (max 36 chars, UUID recommended). Auto-generated if not provided.
Behavior2/5

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

No annotations are provided, so the description alone must disclose behavior, but it only states the generic 'create... accepting funds' action. It does not mention that this initiates a payment flow, requires a return_url, sends webhooks, or has idempotency semantics, which are significant behavioral traits.

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 short and front-loaded with the resource name and endpoint, but it contains redundancy ('Create Payin' / 'Create a new Payin resource'). It is nevertheless brief and free of unnecessary fluff.

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?

This is a complex 8-parameter tool with nested oneOf payment and settlement objects, yet the description offers only the bare 'accepting funds' concept. Without annotations or an output schema, the description is insufficient to orient an agent on workflow, payment methods, or required dependencies.

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 description adds no parameter-level meaning beyond what the input schema already contains, such as required amount, return_url, and payer. With schema description coverage around 75%, the schema itself carries the parameter explanation, so no penalty is applied, but there is no added value from the description.

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 names the specific verb and resource ('Create a new Payin resource') and adds the directional scope 'accepting funds from a Payer,' which clearly distinguishes it from the sibling create_payout tool. The endpoint '[POST /payins]' reinforces the exact operation.

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 phrase 'accepting funds from a Payer' establishes a clear use case for collecting payments, implicitly distinguishing it from create_payout for outgoing funds. However, it does not explicitly state when not to use the tool or mention alternatives, so it stops short of full usage guidance.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/georgi-shulev/yugo-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server