Skip to main content
Glama
daanno

Simplicate MCP Server

by daanno

get_invoices

Retrieve invoices from Simplicate business data to access billing information, track payments, and manage financial records.

Instructions

Retrieve invoices

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNo
offsetNo

Implementation Reference

  • The handler for the 'get_invoices' tool call. It parses input arguments for limit and offset, calls SimplicateService.getInvoices, stringifies the result as JSON, and returns it as text content.
    case 'get_invoices': {
      const invoices = await this.simplicateService.getInvoices({
        limit: (toolArgs.limit as number) || 10,
        offset: (toolArgs.offset as number) || 0,
      });
      return {
        content: [
          {
            type: 'text',
            text: JSON.stringify(invoices, null, 2),
          },
        ],
      };
    }
  • Registration of the 'get_invoices' tool in the ListToolsRequestHandler response, including name, description, and input schema definition.
    {
      name: 'get_invoices',
      description: 'Retrieve invoices from Simplicate',
      inputSchema: {
        type: 'object',
        properties: {
          limit: {
            type: 'number',
            description: 'Maximum number of invoices to return (default: 10)',
          },
          offset: {
            type: 'number',
            description: 'Number of invoices to skip (for pagination)',
          },
        },
      },
    },
  • Input schema definition for the 'get_invoices' tool, specifying optional limit and offset parameters.
    inputSchema: {
      type: 'object',
      properties: {
        limit: {
          type: 'number',
          description: 'Maximum number of invoices to return (default: 10)',
        },
        offset: {
          type: 'number',
          description: 'Number of invoices to skip (for pagination)',
        },
      },
    },
  • The core helper method in SimplicateService that performs the actual API call to fetch invoices from the '/invoices/invoice' endpoint using pagination params.
    async getInvoices(params?: { limit?: number; offset?: number }): Promise<SimplicateInvoice[]> {
      const response = await this.client.get('/invoices/invoice', params);
      return response.data || [];
    }
Behavior1/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure but provides almost none. 'Retrieve invoices' doesn't indicate whether this is a read-only operation, what permissions might be required, whether it supports pagination (though parameters suggest it might), what format invoices are returned in, or any rate limits. For a tool with 2 parameters and no annotation coverage, this is critically insufficient.

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 at just two words. While this represents severe under-specification rather than ideal conciseness, from a pure length perspective it's minimal with zero wasted words. Every word earns its place, though far more content is needed for adequacy.

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

Completeness1/5

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

Given the tool has 2 parameters with 0% schema coverage, no annotations, no output schema, and multiple sibling tools, the description is completely inadequate. It doesn't explain what the tool returns, how parameters work, when to use it, or any behavioral characteristics. For a retrieval tool in a complex system with many alternatives, this description fails to provide necessary context.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The description provides zero information about the 2 parameters (limit and offset). With 0% schema description coverage and no parameter details in the description, the agent has no semantic understanding of what these parameters do, their expected values, or how they affect the retrieval. The description doesn't compensate for the complete lack of schema documentation.

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

Purpose2/5

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

The description 'Retrieve invoices' is a tautology that essentially restates the tool name 'get_invoices'. It specifies the verb 'retrieve' and resource 'invoices', but doesn't differentiate from sibling tools like 'get_invoice' (singular) or provide any scope information about what kind of invoices are retrieved. While it communicates the basic action, it lacks the specificity needed for clear distinction.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/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 when to use 'get_invoices' versus 'get_invoice' (singular), 'search', or other retrieval tools in the sibling list. There are no prerequisites, context requirements, or exclusions provided, leaving the agent with no usage direction.

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/daanno/simplicate-mcp'

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