Skip to main content
Glama
daanno

Simplicate MCP Server

by daanno

get_sales

Retrieve sales records from Simplicate business data to access transaction history, monitor revenue streams, and analyze customer purchases.

Instructions

Retrieve sales records

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNo
offsetNo

Implementation Reference

  • The main handler function for the 'get_sales' tool, which retrieves sales data from the Simplicate '/sales/sale' API endpoint, with optional pagination parameters. Handles errors by returning an empty array.
    async getSales(params?: { limit?: number; offset?: number }): Promise<SimplicateSale[]> {
      try {
        const response = await this.client.get('/sales/sale', params);
        return response.data || [];
      } catch (error) {
        // Sales endpoint may require specific filters
        console.warn('getSales: endpoint returned error, returning empty array');
        return [];
      }
    }
  • TypeScript interface defining the structure of a SimplicateSale object, used as the return type for the getSales handler.
    export interface SimplicateSale {
      id: string;
      sale_number: string;
      subject: string;
      organization?: { id: string; name: string };
      status: string;
      total: number;
    }
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. 'Retrieve' implies a read operation, but it doesn't disclose critical traits like pagination behavior (implied by limit/offset parameters), authentication needs, rate limits, or what happens on errors. This is inadequate for a tool with parameters and no output schema.

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 'Retrieve sales records'—a single, front-loaded sentence that wastes no words. While it may be under-specified, it earns full marks for brevity and structure without redundancy.

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 (2 parameters, 0% schema coverage, no output schema, no annotations), the description is incomplete. It lacks details on behavior, parameter usage, output format, and differentiation from siblings, making it insufficient for effective agent use without additional context.

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

Parameters2/5

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

Schema description coverage is 0%, so the description must compensate for undocumented parameters. It adds no meaning beyond the schema, failing to explain what 'limit' and 'offset' do (e.g., pagination controls), their units, or default values. This leaves parameters semantically unclear.

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 'Retrieve sales records' states the basic action (retrieve) and resource (sales records), which provides a vague purpose. However, it doesn't specify what 'sales records' include or distinguish this tool from similar siblings like 'get_sale' (singular) or 'get_revenue', leaving ambiguity about scope and differentiation.

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. With siblings like 'get_sale' (singular), 'get_revenue', and 'search', the description offers no context on usage scenarios, prerequisites, or exclusions, leaving the agent to guess based on tool names 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/daanno/simplicate-mcp'

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