Skip to main content
Glama
VautlixDevelopment

Vaultix MCP Server

by VautlixDevelopment
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Remote

vaultix_deactivate_payment_link

Deactivate a payment link in the Vaultix system by providing its ID to prevent further transactions.

Instructions

Deactivate a payment link

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesPayment Link ID to deactivate

Implementation Reference

  • src/tools/index.ts:578-579 (handler)
    The handler logic within the tool dispatcher switch statement. It deactivates the payment link by making a POST request to the `/payment-links/{id}/deactivate` endpoint using the VaultixClient.
    case 'vaultix_deactivate_payment_link':
  return client.post(`/payment-links/${args.id}/deactivate`)
  • src/tools/index.ts:352-362 (registration)
    The tool registration object added to the exported `tools` array, defining the name, description, and input schema for the vaultix_deactivate_payment_link tool.
    {
  name: 'vaultix_deactivate_payment_link',
  description: 'Deactivate a payment link',
  inputSchema: {
    type: 'object',
    properties: {
      id: { type: 'string', description: 'Payment Link ID to deactivate' },
    },
    required: ['id'],
  },
},
  • src/tools/index.ts:355-360 (schema)
    The input schema defining the required 'id' parameter for the tool.
    inputSchema: {
  type: 'object',
  properties: {
    id: { type: 'string', description: 'Payment Link ID to deactivate' },
  },
  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 the full burden of behavioral disclosure. It states the action ('deactivate') but does not explain what deactivation entails (e.g., whether it's reversible, requires specific permissions, affects linked transactions, or has side effects). This is a significant gap for a mutation tool with no annotation coverage.

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 ('Deactivate a payment link') that is front-loaded and wastes no words. It directly conveys the core action without unnecessary elaboration, making it highly concise and well-structured.

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 that this is a mutation tool with no annotations, no output schema, and incomplete behavioral context in the description, the description is inadequate. It lacks details on effects, return values, or error conditions, failing to provide a complete understanding for safe and effective use.

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 input schema has 100% description coverage, with the 'id' parameter fully documented. The description does not add any meaning beyond the schema, such as format examples or constraints. Since schema coverage is high, the baseline score of 3 is appropriate, as the description does not compensate but also does not detract.

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 'Deactivate a payment link' clearly states the verb ('deactivate') and resource ('payment link'), making the purpose specific and understandable. However, it does not differentiate from sibling tools like 'vaultix_cancel_charge' or 'vaultix_cancel_payout', which also involve deactivation-like actions, so it lacks explicit sibling distinction.

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, such as when to deactivate vs. cancel or delete related resources. There is no mention of prerequisites, context, or exclusions, leaving usage unclear beyond the basic action.

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