Skip to main content
Glama
jdlar1

Siigo MCP Server

by jdlar1

siigo_create_voucher

Create accounting vouchers in Siigo software to document financial transactions and maintain accurate records.

Instructions

Create a new voucher

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
voucherYesVoucher data

Implementation Reference

  • Core handler implementation for siigo_create_voucher tool. Performs authenticated POST request to Siigo API /v1/vouchers endpoint with provided voucher data.
    async createVoucher(voucher: any): Promise<SiigoApiResponse<any>> {
      return this.makeRequest<any>('POST', '/v1/vouchers', voucher);
    }
  • MCP server handler that receives tool call, extracts voucher args, delegates to SiigoClient.createVoucher, and returns formatted JSON response.
    private async handleCreateVoucher(args: any) {
      const result = await this.siigoClient.createVoucher(args.voucher);
      return { content: [{ type: 'text', text: JSON.stringify(result, null, 2) }] };
    }
  • Defines the input schema and metadata for the siigo_create_voucher tool, used in listTools response for client validation.
    {
      name: 'siigo_create_voucher',
      description: 'Create a new voucher',
      inputSchema: {
        type: 'object',
        properties: {
          voucher: { type: 'object', description: 'Voucher data' },
        },
        required: ['voucher'],
      },
    },
  • src/index.ts:111-112 (registration)
    Registers the dispatch case in the switch statement for handling siigo_create_voucher tool calls within the CallToolRequestSchema handler.
    case 'siigo_create_voucher':
      return await this.handleCreateVoucher(args);
  • Helper method used by createVoucher to handle authentication, HTTP requests to Siigo API, and error handling.
    private async makeRequest<T>(method: string, endpoint: string, data?: any, params?: any): Promise<SiigoApiResponse<T>> {
      await this.authenticate();
    
      try {
        const response: AxiosResponse<SiigoApiResponse<T>> = await this.httpClient.request({
          method,
          url: endpoint,
          data,
          params,
        });
    
        return response.data;
      } catch (error: any) {
        if (error.response?.data) {
          return error.response.data;
        }
        throw new Error(`API request failed: ${error.message}`);
      }
    }
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. 'Create a new voucher' implies a write operation but doesn't specify permissions required, whether it's idempotent, what happens on failure, or any rate limits. For a mutation tool with zero annotation coverage, this leaves critical behavioral traits undocumented, though it doesn't contradict any annotations.

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 extremely concise at three words, which is efficient and front-loaded. However, it's arguably too brief given the lack of context and behavioral details, bordering on under-specification rather than optimal conciseness. It earns a 4 for being direct but loses a point for not including essential clarifying information.

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 complexity of a creation tool with no annotations, no output schema, and nested input objects, the description is incomplete. It doesn't explain what a voucher is, what data it requires, or what the tool returns. With many similar sibling tools, this lack of differentiation and detail makes it inadequate for an agent to use correctly without additional context.

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?

The input schema has 100% description coverage, with the single parameter 'voucher' described as 'Voucher data'. The description adds no additional parameter information beyond what the schema provides. According to the rules, when schema coverage is high (>80%), the baseline score is 3 even with no param info in the description, which applies here.

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 'Create a new voucher' clearly states the action (create) and resource (voucher), making the purpose understandable. However, it doesn't differentiate from sibling tools like siigo_create_credit_note or siigo_create_invoice, which follow the same 'Create a new X' pattern, leaving the specific domain of 'voucher' ambiguous without additional context about what a voucher represents in this system.

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. With many sibling tools for creating different entities (e.g., siigo_create_credit_note, siigo_create_invoice), there's no indication of what a voucher is used for or when it should be created instead of other document types. The lack of context makes it difficult for an agent to choose appropriately.

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