Skip to main content
Glama
daanno

Simplicate MCP Server

by daanno

get_default_services

Retrieve default services configuration from the Simplicate business platform to access predefined service settings for CRM, projects, timesheets, and invoice management.

Instructions

Get default services configuration

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • MCP tool handler case for 'get_default_services' that delegates to SimplicateServiceExtended.getDefaultServices() and formats response as MCP content.
    case 'get_default_services': {
      const data = await this.simplicateService.getDefaultServices();
      return { content: [{ type: 'text', text: JSON.stringify(data, null, 2) }] };
    }
  • Tool registration in ListToolsRequestSchema handler, defining name, description, and empty input schema.
    {
      name: 'get_default_services',
      description: 'Get default services configuration',
      inputSchema: { type: 'object', properties: {} },
    },
  • Core helper method implementation that performs API call to Simplicate's /services/defaultservice endpoint.
    async getDefaultServices(): Promise<SimplicateDefaultService[]> {
      const response = await this.client.get('/services/defaultservice');
      return response.data || [];
    }
  • TypeScript interface defining the structure of default services returned by the tool.
    export interface SimplicateDefaultService {
      id: string;
      default_service_id: string;
      hours_type_id: string;
    }
Behavior2/5

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

No annotations are provided, so the description carries full burden. It states 'Get' implying a read operation, but doesn't disclose behavioral traits such as authentication needs, rate limits, error handling, or what 'default services configuration' entails (e.g., global vs. user-specific). This is a significant gap for a tool with no annotation coverage.

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 with no wasted words. It's front-loaded with the core action and resource, making it easy to parse. Every word earns its place, adhering to best practices 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 has no annotations, no output schema, and 0 parameters, the description is incomplete. It lacks details on what 'default services configuration' returns, how it differs from other 'get' tools, or any behavioral context. For a retrieval tool in a system with many similar siblings, this is inadequate.

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

Parameters4/5

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

The tool has 0 parameters with 100% schema description coverage, so the schema fully documents the absence of inputs. The description doesn't need to add parameter details, and it doesn't contradict the schema. Baseline is 4 for zero parameters, as the description appropriately focuses on purpose without redundant param info.

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 'Get default services configuration' clearly states the action (Get) and resource (default services configuration). It distinguishes from siblings like 'get_services' or 'get_project_services' by specifying 'default' configuration, though it doesn't explicitly contrast them. The purpose is specific but could be more differentiated.

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' or 'get_project_services'. The description implies retrieval of default settings but doesn't specify contexts, prerequisites, or exclusions. This leaves the agent without clear 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