Skip to main content
Glama
VautlixDevelopment

Vaultix MCP Server

vaultix_delete_customer

Remove customer records from the Vaultix payment system by specifying the customer ID to delete.

Instructions

Delete a customer

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesCustomer ID to delete

Implementation Reference

  • The handler logic within the handleToolCall switch statement that deletes a customer by calling the VaultixClient's delete method on the `/customers/{id}` endpoint.
    case 'vaultix_delete_customer':
      return client.delete(`/customers/${args.id}`)
  • The input schema defining the required 'id' parameter as a string for the customer ID.
    inputSchema: {
      type: 'object',
      properties: {
        id: { type: 'string', description: 'Customer ID to delete' },
      },
      required: ['id'],
    },
  • The tool registration object added to the exported 'tools' array, including name, description, and schema.
    {
      name: 'vaultix_delete_customer',
      description: 'Delete a customer',
      inputSchema: {
        type: 'object',
        properties: {
          id: { type: 'string', description: 'Customer ID to delete' },
        },
        required: ['id'],
      },
    },
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 states 'Delete' which implies a destructive mutation, but doesn't elaborate on critical aspects like whether deletion is permanent, requires specific permissions, affects related data (e.g., charges), or has rate limits. This leaves significant gaps for safe and effective use by an AI agent.

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, direct sentence with zero wasted words. It is front-loaded with the core action and resource, making it highly efficient. Every word earns its place, and there is no unnecessary elaboration or redundancy.

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 destructive operation with no annotations and no output schema, the description is insufficiently complete. It lacks details on behavioral traits (e.g., irreversibility, side effects), usage context, or expected outcomes. For a tool that permanently removes data, this minimal description poses risks for an AI agent's decision-making.

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 clearly documented as 'Customer ID to delete'. The description adds no additional parameter information beyond this. According to the rules, when schema coverage is high (>80%), the baseline score is 3 even without param details in the description, which applies here.

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 ('Delete') and resource ('a customer'), making the purpose immediately understandable. It distinguishes from siblings like 'vaultix_update_customer' or 'vaultix_get_customer' by specifying the destructive operation. However, it doesn't specify what 'customer' means in this context (e.g., a payment customer record), which prevents a perfect score.

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 instance, it doesn't mention prerequisites (e.g., customer must exist), consequences (e.g., irreversible deletion), or when to choose deletion over deactivation (if applicable). The presence of sibling tools like 'vaultix_update_customer' suggests alternatives, but the description offers no comparison.

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