Skip to main content
Glama
daanno

Simplicate MCP Server

by daanno

get_project

Retrieve detailed project information from Simplicate using a project ID to access CRM data, timesheets, and invoice records for business management.

Instructions

Get details of a specific project by ID

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
project_idYesProject ID

Implementation Reference

  • MCP tool handler for 'get_project': validates project_id input, fetches project using SimplicateService, returns JSON stringified response.
    case 'get_project': {
      if (!toolArgs.project_id) {
        throw new Error('project_id is required');
      }
      const project = await this.simplicateService.getProjectById(
        toolArgs.project_id as string
      );
      return {
        content: [
          {
            type: 'text',
            text: JSON.stringify(project, null, 2),
          },
        ],
      };
    }
  • Registration of the 'get_project' tool in ListToolsRequestHandler, including name, description, and input schema.
    {
      name: 'get_project',
      description: 'Get details of a specific project by ID',
      inputSchema: {
        type: 'object',
        properties: {
          project_id: {
            type: 'string',
            description: 'The ID of the project to retrieve',
          },
        },
        required: ['project_id'],
      },
    },
  • TypeScript interface defining the structure of project data returned by getProjectById.
    export interface SimplicateProject {
      id: string;
      name: string;
      project_number: string;
      organization?: {
        id: string;
        name: string;
      };
      project_manager?: {
        id: string;
        name: string;
      };
      start_date?: string;
      end_date?: string;
      budget?: number;
      status?: string;
    }
  • Implementation of getProjectById in SimplicateService: makes API call to fetch single project by ID.
    async getProjectById(projectId: string): Promise<SimplicateProject> {
      const response = await this.client.get(`/projects/project/${projectId}`);
      return response.data;
    }
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. It states the tool retrieves details but doesn't clarify what 'details' include, whether it's a read-only operation, what happens with invalid IDs, or if authentication is required. For a tool with zero annotation coverage, this leaves significant gaps in understanding its behavior.

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 that front-loads the core action ('Get details') without unnecessary words. Every part of the sentence earns its place by specifying the resource and lookup method.

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 for a tool that likely returns structured project data. It doesn't hint at the return format, error conditions, or any behavioral traits, leaving the agent with insufficient context to use it effectively beyond the basic parameter.

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

Parameters3/5

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

The schema description coverage is 100%, with the single parameter 'project_id' documented as 'Project ID' in the schema. The description adds no additional meaning beyond implying the parameter is required for lookup, which is already clear from the schema. This meets the baseline score when schema coverage is high.

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 clearly states the verb ('Get details') and resource ('specific project by ID'), making the purpose immediately understandable. It doesn't explicitly differentiate from sibling tools like 'get_projects' (plural) or 'update_project', but the specificity of 'by ID' implies it retrieves a single entity rather than a list.

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 sibling tools like 'get_projects' for listing multiple projects or 'update_project' for modifications, nor does it specify prerequisites such as needing a valid project ID.

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