Skip to main content
Glama
VautlixDevelopment

Vaultix MCP Server

vaultix_update_customer

Modify customer details like name, email, or phone number in the Vaultix payment system using their customer ID.

Instructions

Update a customer

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesCustomer ID
nameNoNew name
emailNoNew email
phoneNoNew phone

Implementation Reference

  • Handler logic in the switch statement that destructures the customer ID from args and calls client.put to update the customer via the Vaultix API.
    case 'vaultix_update_customer':
      const { id: custId, ...custUpdates } = args
      return client.put(`/customers/${custId}`, custUpdates)
  • Tool definition including name, description, and input schema specifying parameters for updating a customer (id required, optional name, email, phone).
    {
      name: 'vaultix_update_customer',
      description: 'Update a customer',
      inputSchema: {
        type: 'object',
        properties: {
          id: { type: 'string', description: 'Customer ID' },
          name: { type: 'string', description: 'New name' },
          email: { type: 'string', description: 'New email' },
          phone: { type: 'string', description: 'New phone' },
        },
        required: ['id'],
      },
    },
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. 'Update' implies a mutation operation, but the description doesn't specify whether this requires specific permissions, what happens on success/failure, whether changes are reversible, or if there are rate limits. This leaves significant gaps for a mutation tool.

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 at just three words, with zero wasted language. It's front-loaded with the essential action and resource, making it efficient for quick understanding.

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?

For a mutation tool with no annotations and no output schema, the description is insufficient. It doesn't explain what values are returned, error conditions, or behavioral nuances. Given the complexity of customer updates and the lack of structured documentation, more context is needed.

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. The description adds no additional parameter information beyond what's in the schema, maintaining the baseline score of 3 for adequate but not enhanced parameter documentation.

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 ('Update') and resource ('a customer'), making the purpose immediately understandable. However, it doesn't differentiate this tool from its sibling 'vaultix_update_product' or explain what aspects of a customer can be updated beyond what's implied by the parameters.

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 about when to use this tool versus alternatives like 'vaultix_get_customer' for reading or 'vaultix_delete_customer' for removal. The description doesn't mention prerequisites (e.g., needing an existing customer ID) or contextual constraints.

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