Skip to main content
Glama
jdlar1

Siigo MCP Server

by jdlar1

siigo_get_payment_receipt

Retrieve a specific payment receipt from Siigo accounting software using its unique ID to access transaction details and records.

Instructions

Get a specific payment receipt by ID

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesPayment receipt ID

Implementation Reference

  • The core implementation of the tool logic: makes an authenticated GET request to the Siigo API endpoint `/v1/payment-receipts/{id}` using the shared makeRequest method.
    async getPaymentReceipt(id: string): Promise<SiigoApiResponse<any>> {
      return this.makeRequest<any>('GET', `/v1/payment-receipts/${id}`);
    }
  • MCP tool handler wrapper: extracts 'id' from arguments, calls SiigoClient.getPaymentReceipt, and formats the response as MCP content (JSON string).
    private async handleGetPaymentReceipt(args: any) {
      const result = await this.siigoClient.getPaymentReceipt(args.id);
      return { content: [{ type: 'text', text: JSON.stringify(result, null, 2) }] };
    }
  • src/index.ts:585-595 (registration)
    Registration of the tool in the MCP server's getTools() method, defining name, description, and input schema (requires 'id' string).
    {
      name: 'siigo_get_payment_receipt',
      description: 'Get a specific payment receipt by ID',
      inputSchema: {
        type: 'object',
        properties: {
          id: { type: 'string', description: 'Payment receipt ID' },
        },
        required: ['id'],
      },
    },
  • Input schema definition for the tool: expects an object with required 'id' field (string).
      inputSchema: {
        type: 'object',
        properties: {
          id: { type: 'string', description: 'Payment receipt ID' },
        },
        required: ['id'],
      },
    },
  • Dispatch case in the main CallToolRequestSchema handler switch statement that routes to the specific tool handler.
    case 'siigo_get_payment_receipt':
      return await this.handleGetPaymentReceipt(args);
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 basic action. It doesn't disclose behavioral traits like whether this is a read-only operation, authentication requirements, error handling, rate limits, or response format, which are critical for a retrieval tool.

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 directly states the tool's function with zero wasted words. It's appropriately sized and front-loaded, 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 for a retrieval tool. It lacks details on return values, error conditions, or behavioral context, leaving significant gaps for an agent to understand how 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?

The input schema has 100% description coverage, clearly documenting the 'id' parameter. The description adds no additional meaning beyond the schema, such as ID format or examples, so it meets the baseline for high schema coverage without compensating value.

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 ('a specific payment receipt by ID'), making the purpose unambiguous. However, it doesn't explicitly differentiate from its sibling 'siigo_get_payment_receipts' (plural), which likely retrieves multiple receipts, so it misses full sibling distinction.

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. It doesn't mention the sibling 'siigo_get_payment_receipts' for listing multiple receipts or other retrieval tools, leaving the agent without context for tool selection.

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