Skip to main content
Glama
jdlar1

Siigo MCP Server

by jdlar1

siigo_get_trial_balance

Retrieve trial balance reports from Siigo accounting software to analyze financial data by specifying account ranges, time periods, and tax difference inclusion.

Instructions

Get trial balance report

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
account_startNoStarting account code
account_endNoEnding account code
yearYesYear
month_startYesStarting month (1-13)
month_endYesEnding month (1-13)
includes_tax_differenceYesInclude tax differences

Implementation Reference

  • Core implementation of the siigo_get_trial_balance tool: makes authenticated GET request to Siigo API /v1/trial-balance endpoint with the provided parameters.
    async getTrialBalance(params: {
      account_start?: string;
      account_end?: string;
      year: number;
      month_start: number;
      month_end: number;
      includes_tax_difference: boolean;
    }): Promise<SiigoApiResponse<any>> {
      return this.makeRequest<any>('GET', '/v1/trial-balance', undefined, params);
    }
  • MCP server wrapper handler that calls SiigoClient.getTrialBalance and returns JSON-formatted response.
    private async handleGetTrialBalance(args: any) {
      const result = await this.siigoClient.getTrialBalance(args);
      return { content: [{ type: 'text', text: JSON.stringify(result, null, 2) }] };
    }
  • src/index.ts:735-749 (registration)
    Tool registration in MCP server, including name, description, and input schema validation.
      name: 'siigo_get_trial_balance',
      description: 'Get trial balance report',
      inputSchema: {
        type: 'object',
        properties: {
          account_start: { type: 'string', description: 'Starting account code' },
          account_end: { type: 'string', description: 'Ending account code' },
          year: { type: 'number', description: 'Year' },
          month_start: { type: 'number', description: 'Starting month (1-13)' },
          month_end: { type: 'number', description: 'Ending month (1-13)' },
          includes_tax_difference: { type: 'boolean', description: 'Include tax differences' },
        },
        required: ['year', 'month_start', 'month_end', 'includes_tax_difference'],
      },
    },
  • Input schema definition for siigo_get_trial_balance tool parameters.
        type: 'object',
        properties: {
          account_start: { type: 'string', description: 'Starting account code' },
          account_end: { type: 'string', description: 'Ending account code' },
          year: { type: 'number', description: 'Year' },
          month_start: { type: 'number', description: 'Starting month (1-13)' },
          month_end: { type: 'number', description: 'Ending month (1-13)' },
          includes_tax_difference: { type: 'boolean', description: 'Include tax differences' },
        },
        required: ['year', 'month_start', 'month_end', 'includes_tax_difference'],
      },
    },
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 'Get trial balance report', implying a read-only operation, but does not disclose behavioral traits such as authentication requirements, rate limits, data format, or whether it's a safe operation. This leaves significant gaps in understanding how the tool behaves.

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 with a single phrase, 'Get trial balance report', which is front-loaded and wastes no words. It efficiently communicates the core purpose without unnecessary elaboration, making it highly structured for quick comprehension.

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 tool's complexity (6 parameters, no output schema, and no annotations), the description is insufficient. It lacks details on return values, error handling, or operational context, leaving the agent with incomplete information to effectively use the tool beyond basic parameter input.

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 all parameters well-documented in the input schema. The description adds no additional meaning beyond the schema, such as explaining parameter interactions or usage examples. Baseline 3 is appropriate as 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 trial balance report' clearly indicates a retrieval action ('Get') and specifies the resource ('trial balance report'), which distinguishes it from siblings like 'siigo_get_trial_balance_by_third'. However, it lacks specificity about what a trial balance entails (e.g., financial summary of accounts), making it somewhat vague but still functional.

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. While siblings include 'siigo_get_trial_balance_by_third', the description does not mention this or any other context for selection, leaving usage entirely implicit based on the tool name alone.

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/jdlar1/siigo-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server