Skip to main content
Glama
daanno

Simplicate MCP Server

by daanno

get_quotes

Retrieve sales quotes from Simplicate business data to access pricing information and proposal details for customer transactions.

Instructions

Retrieve sales quotes

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNo
offsetNo

Implementation Reference

  • Type definition (schema) for SimplicateQuote objects returned by getQuotes
    export interface SimplicateQuote {
      id: string;
      quote_number: string;
      subject: string;
      organization?: { id: string; name: string };
      status: string;
      total: number;
      created_at: string;
    }
  • Handler function that executes the get_quotes tool logic by calling the Simplicate API endpoint '/sales/quote' and returning the list of quotes
    async getQuotes(params?: { limit?: number; offset?: number }): Promise<SimplicateQuote[]> {
      const response = await this.client.get('/sales/quote', params);
      return response.data || [];
    }
  • Dynamic helper/dispatcher in HTTP MCP server that maps tool name 'get_quotes' to service.getQuotes() execution
    async function dispatchTool(toolName: string, args: any) {
      const method = toMethodName(toolName);
      // heuristic param extraction
      const params: any[] = [];
      if (args && typeof args === 'object') {
        // common id patterns
        const idKeys = ['project_id','organization_id','person_id','task_id','service_id','invoice_id','id'];
        let foundId = false;
        for (const k of idKeys) {
          if (k in args) {
            params.push(args[k]);
            foundId = true;
            break;
          }
        }
        if (args.data) params.push(args.data);
        if (!foundId && params.length === 0) params.push(args);
      } else if (args !== undefined) {
        params.push(args);
      }
    
      // @ts-ignore - dynamic call
      if (typeof (service as any)[method] === 'function') {
        // call and return
        // Some methods expect a single primitive id; spread params
        return await (service as any)[method](...params);
      }
    
      throw new Error(`Unknown tool/method: ${toolName} -> ${method}`);
    }
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. 'Retrieve' implies a read operation, but it doesn't specify whether this is paginated (despite limit/offset parameters), what authentication is needed, rate limits, or what format the quotes are returned in. Significant behavioral details are missing.

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, with no wasted language. It's front-loaded with the core purpose, though this brevity comes at the cost of completeness.

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?

For a tool with 2 parameters, 0% schema coverage, no annotations, and no output schema, the description is inadequate. It doesn't explain what 'sales quotes' encompasses, how results are returned, or provide any context about the retrieval operation. The agent would struggle to use this tool effectively.

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 but provides no parameter information. The two parameters (limit, offset) are completely undocumented in both schema and description, leaving their purpose and usage ambiguous. The description adds zero value beyond the schema.

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 'Retrieve sales quotes' clearly states the verb ('Retrieve') and resource ('sales quotes'), making the tool's purpose immediately understandable. However, it doesn't differentiate from sibling tools like 'get_quote' (singular) or 'get_sales', leaving some ambiguity about scope.

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 like 'get_quote' (singular), 'get_sales', or 'search'. There's no mention of context, prerequisites, or exclusions, leaving the agent to infer usage from the name 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