Skip to main content
Glama
daanno

Simplicate MCP Server

by daanno

get_service

Retrieve detailed service information by ID from the Simplicate business platform, enabling access to specific service records for project management and client operations.

Instructions

Get specific service by ID

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
service_idYes

Implementation Reference

  • MCP CallToolRequest handler case for 'get_service': validates service_id parameter and delegates to simplicateService.getServiceById, returning JSON stringified response.
    case 'get_service': {
      if (!toolArgs.service_id) throw new Error('service_id is required');
      const data = await this.simplicateService.getServiceById(toolArgs.service_id);
      return { content: [{ type: 'text', text: JSON.stringify(data, null, 2) }] };
  • Tool registration in ListToolsRequest handler: defines name, description, and input schema for 'get_service'.
    {
      name: 'get_service',
      description: 'Get specific service by ID',
      inputSchema: {
        type: 'object',
        properties: { service_id: { type: 'string' } },
        required: ['service_id'],
      },
    },
  • TypeScript interface defining the shape of SimplicateService returned by getServiceById.
    export interface SimplicateService {
      id: string;
      name: string;
      price: number;
      cost_price?: number;
      invoice_method?: string;
    }
  • Core helper method getServiceById: performs HTTP GET to Simplicate API endpoint `/services/service/{serviceId}` and returns the service data.
    async getServiceById(serviceId: string): Promise<SimplicateService> {
      const response = await this.client.get(`/services/service/${serviceId}`);
      return response.data;
    }
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 such as whether it's read-only (implied by 'Get' but not confirmed), error responses for invalid IDs, authentication needs, rate limits, or return format. This leaves significant gaps for agent decision-making.

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 a single, front-loaded sentence that directly states the tool's function. There is no wasted verbiage, making it efficient for quick understanding, though it sacrifices detail for brevity.

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 simplicity (1 parameter, no output schema, no annotations), the description is incomplete. It lacks details on return values, error cases, and how it fits into the broader context of sibling tools. For a basic retrieval tool, more context on behavior and usage would improve agent effectiveness.

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?

The input schema has 1 parameter with 0% description coverage, and the description adds minimal meaning beyond the schema. It mentions 'by ID' which clarifies the parameter's purpose, but doesn't specify ID format, constraints, or examples. This partially compensates for the low schema coverage but remains inadequate.

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 'Get specific service by ID' clearly states the verb ('Get') and resource ('service'), but it's vague about what 'Get' entails—does it retrieve details, metadata, or something else? It distinguishes from sibling 'get_services' (plural) by specifying 'by ID', but lacks precision about the scope of 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 on when to use this tool versus alternatives like 'get_services' (for listing) or 'get_project_services' (for context-specific services). The description implies usage for a known service ID, but there's no explicit advice on prerequisites, error handling, or sibling tool comparisons.

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