Skip to main content
Glama
VautlixDevelopment

Vaultix MCP Server

vaultix_create_payment_link

Generate shareable payment links for Brazilian transactions using PIX or credit cards. Specify amount in cents, add descriptions, set usage limits, and configure redirect URLs after payment completion.

Instructions

Create a shareable payment link. Amount in cents.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
amountYesAmount in cents (minimum 100)
descriptionNoLink description
payment_methodsNoAllowed methods: pix, credit_card
success_urlNoRedirect URL after payment
max_usesNoMaximum number of uses

Implementation Reference

  • The core handler logic for the vaultix_create_payment_link tool. It makes a POST request to the Vaultix API's /payment-links endpoint using the provided input arguments via the VaultixClient.
    case 'vaultix_create_payment_link':
      return client.post('/payment-links', {
        amount: args.amount,
        description: args.description,
        payment_methods: args.payment_methods,
        success_url: args.success_url,
        max_uses: args.max_uses,
      })
  • The schema definition for the vaultix_create_payment_link tool, specifying the name, description, and inputSchema for MCP validation.
    {
      name: 'vaultix_create_payment_link',
      description: 'Create a shareable payment link. Amount in cents.',
      inputSchema: {
        type: 'object',
        properties: {
          amount: { type: 'number', description: 'Amount in cents (minimum 100)' },
          description: { type: 'string', description: 'Link description' },
          payment_methods: { type: 'array', items: { type: 'string' }, description: 'Allowed methods: pix, credit_card' },
          success_url: { type: 'string', description: 'Redirect URL after payment' },
          max_uses: { type: 'number', description: 'Maximum number of uses' },
        },
        required: ['amount'],
      },
    },
  • src/index.ts:44-46 (registration)
    Registers the list of tools (including vaultix_create_payment_link) with the MCP server by handling ListToolsRequestSchema.
    server.setRequestHandler(ListToolsRequestSchema, async () => {
      return { tools }
    })
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 mentions the amount is in cents but lacks critical details such as authentication requirements, rate limits, whether the link is reusable or single-use, or what happens upon creation (e.g., returns a URL). This leaves significant gaps in understanding the tool's behavior.

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 extremely concise with two short sentences that are front-loaded and waste no words. Every part ('Create a shareable payment link. Amount in cents.') directly contributes to understanding the tool's purpose and a key parameter detail.

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 of a payment creation tool with no annotations and no output schema, the description is insufficient. It doesn't explain what is returned (e.g., a URL or ID), error conditions, or side effects, making it incomplete for effective agent use despite the concise structure.

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 already documents all parameters thoroughly (e.g., amount in cents with minimum, allowed payment methods). The description adds minimal value by reiterating 'Amount in cents' but doesn't provide additional context beyond what the schema specifies, aligning with the baseline for high 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 ('Create a shareable payment link') and specifies the resource ('payment link'), making the purpose evident. However, it doesn't explicitly differentiate from sibling tools like 'vaultix_create_charge' or 'vaultix_get_payment_link', which would require mentioning that this is for generating a reusable link rather than a direct charge or retrieval.

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. For example, it doesn't compare to 'vaultix_create_charge' for immediate payments or 'vaultix_get_payment_link' for viewing existing links, leaving the agent without context for selection among siblings.

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/VautlixDevelopment/mcpVaultix'

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