Skip to main content
Glama
daanno

Simplicate MCP Server

by daanno

get_project_services

Retrieve services and items associated with a specific project to access detailed project information and manage project-related activities.

Instructions

Get services/items for a specific project

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
project_idYesProject ID

Implementation Reference

  • Main MCP tool handler for 'get_project_services'. Validates project_id input, delegates to SimplicateServiceExtended.getProjectServices(), formats JSON response.
    case 'get_project_services': {
      if (!toolArgs.project_id) throw new Error('project_id is required');
      const data = await this.simplicateService.getProjectServices(toolArgs.project_id);
      return { content: [{ type: 'text', text: JSON.stringify(data, null, 2) }] };
    }
  • Tool registration in ListTools handler: defines name, description, and input schema for get_project_services.
    {
      name: 'get_project_services',
      description: 'Get services/items for a specific project',
      inputSchema: {
        type: 'object',
        properties: { project_id: { type: 'string', description: 'Project ID' } },
        required: ['project_id'],
      },
    },
  • TypeScript interface defining the structure of project services returned by the tool.
    export interface SimplicateProjectService {
      id: string;
      project_id: string;
      name: string;
      price: number;
      amount: number;
    }
  • Helper method that performs the actual API call to retrieve services for a given project from Simplicate backend.
    async getProjectServices(projectId: string): Promise<SimplicateProjectService[]> {
      const response = await this.client.get(`/projects/service`, { project_id: projectId });
      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 the full burden of behavioral disclosure. It only states the basic action without details on permissions, rate limits, pagination, or response format. This is inadequate for a tool that likely returns data.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/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 and to the point, though it could be slightly more informative without losing conciseness.

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 lack of annotations and output schema, the description is incomplete. It doesn't explain what 'services/items' means, how results are returned, or any behavioral traits. For a data retrieval tool with no structured support, this leaves significant gaps.

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 input schema has 100% description coverage, so the baseline is 3. The description adds minimal value by implying the parameter is used to scope the query to a specific project, but it doesn't explain semantics beyond what the schema provides. Since there's only one parameter, a score of 4 reflects adequate but not exceptional clarity.

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 services/items for a specific project' clearly states the action (get) and resource (services/items), but it's vague about what 'services/items' entails and doesn't differentiate from siblings like 'get_services' or 'get_default_services'. It avoids tautology but lacks specificity.

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. It doesn't mention prerequisites, context, or exclusions, leaving the agent to infer usage from the name alone among many sibling tools.

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