Skip to main content
Glama
VautlixDevelopment

Vaultix MCP Server

vaultix_delete_product

Remove a product from the Vaultix payment system by specifying its unique identifier to manage your catalog effectively.

Instructions

Delete a product

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesProduct ID to delete

Implementation Reference

  • Registration of the vaultix_delete_product tool in the tools array, including name, description, and input schema definition.
    {
      name: 'vaultix_delete_product',
      description: 'Delete a product',
      inputSchema: {
        type: 'object',
        properties: {
          id: { type: 'string', description: 'Product ID to delete' },
        },
        required: ['id'],
      },
    },
  • Input schema for vaultix_delete_product tool defining the required 'id' parameter.
    inputSchema: {
      type: 'object',
      properties: {
        id: { type: 'string', description: 'Product ID to delete' },
      },
      required: ['id'],
  • Handler logic for vaultix_delete_product: calls client.delete on the products endpoint with the provided product ID.
    case 'vaultix_delete_product':
      return client.delete(`/products/${args.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 but only states the action without behavioral details. It doesn't disclose if deletion is permanent, requires specific permissions, has side effects (e.g., affecting related charges), or returns confirmation. For a destructive operation, this lack of transparency is a significant gap.

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 ('Delete a product') with no wasted words, making it easy to parse. It front-loads the core action effectively. For a simple tool with one parameter, this brevity is appropriate and efficient.

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 this is a destructive mutation tool with no annotations and no output schema, the description is inadequate. It doesn't explain what happens upon deletion, error conditions, or return values. For a tool that permanently removes data, more context is needed to ensure safe and correct usage.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/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. The description doesn't add any parameter details beyond the schema, but with high schema coverage and only one parameter, the baseline is strong. It implicitly confirms the parameter's purpose through the tool name.

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 product'), which is specific and unambiguous. It distinguishes from sibling tools like 'vaultix_get_product' or 'vaultix_update_product' by focusing on deletion. However, it doesn't explicitly mention what type of product or system context, 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?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., product must exist), consequences (e.g., irreversible deletion), or when to choose deletion over deactivation (though no deactivation tool exists in siblings). This leaves the agent with minimal context for decision-making.

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