Skip to main content
Glama
VautlixDevelopment

Vaultix MCP Server

by VautlixDevelopment
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Remote

vaultix_get_transactions_summary

Retrieve a summary of payment transactions for a specified period to analyze revenue and activity trends.

Instructions

Get transaction summary for a period

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
periodNoPeriod for summary (default: 30d)

Implementation Reference

  • src/tools/index.ts:556-558 (handler)
    Handler implementation for the vaultix_get_transactions_summary tool. It retrieves the transaction summary from the Vaultix API endpoint '/transactions/summary' with the specified period or defaults to '30d'.
    case 'vaultix_get_transactions_summary':
  return client.get('/transactions/summary', { period: args.period || '30d' })
  • src/tools/index.ts:303-312 (registration)
    Tool registration in the tools array, including name, description, and input schema definition.
    {
  name: 'vaultix_get_transactions_summary',
  description: 'Get transaction summary for a period',
  inputSchema: {
    type: 'object',
    properties: {
      period: { type: 'string', enum: ['24h', '7d', '30d', '90d'], description: 'Period for summary (default: 30d)' },
    },
  },
},
  • src/tools/index.ts:306-311 (schema)
    Input schema for the vaultix_get_transactions_summary tool, defining the 'period' parameter.
    inputSchema: {
  type: 'object',
  properties: {
    period: { type: 'string', enum: ['24h', '7d', '30d', '90d'], description: 'Period for summary (default: 30d)' },
  },
},

Tool Definition Quality

C2.6/5.0
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 disclosing behavioral traits like whether it's read-only (implied by 'Get'), authentication needs, rate limits, error handling, or output format. It lacks details on what 'summary' entails, leaving gaps in understanding the tool's behavior.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, efficient sentence with no wasted words, making it easy to parse. However, it could be more front-loaded with key details (e.g., 'Get aggregated transaction data'), but its brevity is appropriate for the simple tool.

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 for a tool that likely returns aggregated financial data. It doesn't explain what the summary includes (e.g., counts, amounts, currency) or handle complexity like authentication, making it insufficient for an agent to use effectively without guesswork.

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%, with the parameter 'period' fully documented in the schema (enum values and default). The description adds no additional meaning beyond implying temporal filtering, so it meets the baseline of 3 where the schema handles parameter documentation adequately.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'Get transaction summary for a period' states the verb ('Get') and resource ('transaction summary'), but it's vague about what constitutes a 'summary' (e.g., totals, counts, trends) and doesn't differentiate from siblings like 'vaultix_get_transaction' (singular) or 'vaultix_list_transactions' (detailed list). It provides basic purpose but lacks specificity.

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 given on when to use this tool versus alternatives such as 'vaultix_list_transactions' for detailed records or 'vaultix_get_balance' for financial overview. The description implies usage for aggregated data over a period but offers no explicit when/when-not instructions or sibling comparisons.

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