Skip to main content
Glama
VautlixDevelopment

Vaultix MCP Server

vaultix_get_order

Retrieve order details by ID to view transaction information, including expanded item data when needed.

Instructions

Retrieve an order by ID

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesOrder ID
expandNoExpand items

Implementation Reference

  • Tool registration in the exported tools array, including name, description, and input schema for validation.
    {
      name: 'vaultix_get_order',
      description: 'Retrieve an order by ID',
      inputSchema: {
        type: 'object',
        properties: {
          id: { type: 'string', description: 'Order ID' },
          expand: { type: 'string', enum: ['items'], description: 'Expand items' },
        },
        required: ['id'],
      },
    },
  • Handler implementation within the handleToolCall switch statement. Retrieves the order by making a GET request to `/orders/{id}` with optional expand query parameter using the VaultixClient.
    case 'vaultix_get_order':
      return client.get(`/orders/${args.id}`, { expand: args.expand })
  • src/index.ts:44-46 (registration)
    MCP server registration of all tools via ListToolsRequestHandler, providing the imported tools array which includes vaultix_get_order.
    server.setRequestHandler(ListToolsRequestSchema, async () => {
      return { tools }
    })
  • Tool call dispatcher in MCP server that invokes the specific handleToolCall function for the requested tool name.
    try {
      const result = await handleToolCall(client, name, args || {})
      return {
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. It states 'Retrieve' which implies a read-only operation, but doesn't disclose behavioral traits like authentication needs, rate limits, error handling, or what data is returned. This is a significant gap for a 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 with zero waste. It's front-loaded and gets straight to the point, making it easy to parse quickly.

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. It doesn't explain what an 'order' entails in this context, what fields are returned, or any prerequisites. For a retrieval tool in a payment system, more context is needed to use it effectively.

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 fully documents both parameters ('id' and 'expand'). The description adds no additional meaning beyond implying retrieval by ID, which is already clear from the schema. Baseline 3 is appropriate as the schema does the heavy lifting.

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 ('an order by ID'), making the purpose immediately understandable. It doesn't differentiate from sibling tools like 'vaultix_get_charge' or 'vaultix_get_customer' which follow the same pattern, but the specificity is adequate.

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 example, it doesn't mention 'vaultix_list_orders' for listing multiple orders or clarify if this is for detailed retrieval versus summary. The description only states what it does, not when to choose it.

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