Skip to main content
Glama
jdlar1

Siigo MCP Server

by jdlar1

siigo_get_payment_receipts

Retrieve payment receipt records from Siigo accounting software. Use this tool to access and manage payment documentation for invoices and transactions.

Instructions

Get list of payment receipts from Siigo

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNoPage number
page_sizeNoNumber of items per page

Implementation Reference

  • MCP tool handler that delegates to SiigoClient.getPaymentReceipts and formats the response as MCP content.
    private async handleGetPaymentReceipts(args: any) {
      const result = await this.siigoClient.getPaymentReceipts(args);
      return { content: [{ type: 'text', text: JSON.stringify(result, null, 2) }] };
    }
  • Core implementation in SiigoClient that makes the authenticated GET request to Siigo API endpoint /v1/payment-receipts.
    async getPaymentReceipts(params?: { page?: number; page_size?: number }): Promise<SiigoApiResponse<any>> {
      return this.makeRequest<any>('GET', '/v1/payment-receipts', undefined, params);
    }
  • Input schema definition for the tool, defining optional pagination parameters.
    inputSchema: {
      type: 'object',
      properties: {
        page: { type: 'number', description: 'Page number' },
        page_size: { type: 'number', description: 'Number of items per page' },
      },
    },
  • src/index.ts:574-584 (registration)
    Tool registration in the list returned by getTools() for ListToolsRequest.
    {
      name: 'siigo_get_payment_receipts',
      description: 'Get list of payment receipts from Siigo',
      inputSchema: {
        type: 'object',
        properties: {
          page: { type: 'number', description: 'Page number' },
          page_size: { type: 'number', description: 'Number of items per page' },
        },
      },
    },
  • Generic helper method used by all API calls, handling authentication and request execution.
    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?

With no annotations provided, the description carries full burden for behavioral disclosure. While 'Get list' implies a read operation, the description doesn't mention authentication requirements, rate limits, error conditions, or what format the returned data will have. It also doesn't explain that this is a paginated endpoint (implied by the parameters but not stated).

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 that communicates the core purpose without unnecessary words. It's appropriately sized for a simple list retrieval tool and is front-loaded with the essential information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple read operation with good schema coverage but no annotations or output schema, the description is minimally adequate. It states what the tool does but lacks important context about authentication, error handling, return format, and differentiation from similar tools. The absence of an output schema means the description should ideally provide more information about what data is returned.

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 clear parameter documentation, so the baseline is 3. The tool description adds no additional parameter information beyond what's already in the schema, but doesn't need to compensate for any gaps since schema coverage is complete.

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 verb ('Get') and resource ('list of payment receipts from Siigo'), making the purpose immediately understandable. However, it doesn't differentiate this tool from its sibling 'siigo_get_payment_receipt' (singular), which appears to retrieve a single receipt versus this tool's list retrieval.

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 about when to use this tool versus alternatives. The description doesn't mention the pagination parameters or explain when this list retrieval is appropriate compared to the singular 'siigo_get_payment_receipt' tool or other data retrieval tools in the system.

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