Skip to main content
Glama
VautlixDevelopment

Vaultix MCP Server

by VautlixDevelopment
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Remote

vaultix_get_payment_link

Retrieve a payment link using its unique ID to access payment details and transaction information for processing.

Instructions

Retrieve a payment link by ID

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesPayment Link ID (plink_...)

Implementation Reference

  • src/tools/index.ts:569-570 (handler)
    Handler implementation for 'vaultix_get_payment_link' tool. It retrieves the payment link details by calling client.get on the '/payment-links/{id}' endpoint.
    case 'vaultix_get_payment_link':
  return client.get(`/payment-links/${args.id}`)
  • src/tools/index.ts:330-340 (schema)
    Schema definition for 'vaultix_get_payment_link' tool, specifying the input schema that requires a 'id' parameter of type string.
    {
  name: 'vaultix_get_payment_link',
  description: 'Retrieve a payment link by ID',
  inputSchema: {
    type: 'object',
    properties: {
      id: { type: 'string', description: 'Payment Link ID (plink_...)' },
    },
    required: ['id'],
  },
},
  • src/tools/index.ts:330-340 (registration)
    The tool 'vaultix_get_payment_link' is registered in the 'tools' export array as a Tool object.
    {
  name: 'vaultix_get_payment_link',
  description: 'Retrieve a payment link by ID',
  inputSchema: {
    type: 'object',
    properties: {
      id: { type: 'string', description: 'Payment Link ID (plink_...)' },
    },
    required: ['id'],
  },
},

Tool Definition Quality

C2.9/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 full burden for behavioral disclosure. It states 'Retrieve' which implies a read-only operation, but doesn't clarify permissions needed, rate limits, error handling, or what data is returned (e.g., link status, amount). For a tool with zero annotation coverage, this lacks critical operational context.

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, efficient sentence that front-loads the core purpose without unnecessary words. Every part ('Retrieve a payment link by ID') earns its place by specifying the action, resource, and key input. There is no redundancy or structural waste.

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 no annotations and no output schema, the description is incomplete for a retrieval tool. It doesn't explain what data is returned (e.g., link details, status), error cases, or system behavior. While the schema covers the single parameter, the overall context for an agent to use the tool effectively is lacking.

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%, with the parameter 'id' fully documented in the schema as 'Payment Link ID (plink_...)'. The description adds no additional meaning beyond this, such as format examples or validation rules. With high schema coverage, the baseline score of 3 is appropriate as the description doesn't compensate but doesn't need to.

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 ('Retrieve') and resource ('payment link by ID'), making the purpose unambiguous. It distinguishes from siblings like 'vaultix_list_payment_links' by specifying retrieval of a single item via ID rather than listing multiple items. However, it doesn't explicitly contrast with other 'get_' tools (e.g., 'vaultix_get_charge'), which slightly limits differentiation.

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 provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., needing a payment link ID), exclusions (e.g., not for creating or listing links), or direct comparisons to siblings like 'vaultix_list_payment_links' for bulk retrieval. This leaves usage context entirely implicit.

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