Skip to main content
Glama
daanno

Simplicate MCP Server

by daanno

create_project

Create new projects in Simplicate with essential details including project name, organization, manager, start date, and budget for effective project management.

Instructions

Create a new project

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
budgetNoProject budget
nameYesProject name
organization_idNoOrganization ID
project_manager_idNoProject manager employee ID
start_dateNoStart date (YYYY-MM-DD)

Implementation Reference

  • MCP CallToolRequestSchema handler case for 'create_project' tool. Delegates execution to SimplicateServiceExtended.createProject with tool arguments and formats response as MCP content.
    case 'create_project': {
      const data = await this.simplicateService.createProject(toolArgs);
      return { content: [{ type: 'text', text: JSON.stringify(data, null, 2) }] };
  • Tool registration in ListToolsRequestSchema handler. Defines name, description, and input schema validation for 'create_project'.
    {
      name: 'create_project',
      description: 'Create a new project',
      inputSchema: {
        type: 'object',
        properties: {
          name: { type: 'string', description: 'Project name' },
          organization_id: { type: 'string', description: 'Organization ID' },
          project_manager_id: { type: 'string', description: 'Project manager employee ID' },
          start_date: { type: 'string', description: 'Start date (YYYY-MM-DD)' },
          budget: { type: 'number', description: 'Project budget' },
        },
        required: ['name'],
      },
    },
  • Supporting utility method in SimplicateServiceExtended that performs the actual HTTP POST request to Simplicate API endpoint '/projects/project' to create the project.
    async createProject(data: Partial<SimplicateProject>): Promise<SimplicateProject> {
      const response = await this.client.post('/projects/project', data);
      return response.data;
    }
  • TypeScript interface defining the SimplicateProject structure used for input/output typing in createProject method.
    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;
    }
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. 'Create a new project' implies a write/mutation operation, but it doesn't disclose behavioral traits like required permissions, whether it's idempotent, what happens on failure, or the expected response format. For a creation tool with zero annotation coverage, this is a significant gap in transparency.

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 three words, front-loaded with the core action. There's no wasted language or redundancy. It efficiently communicates the basic purpose without unnecessary elaboration.

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 complexity of a creation tool with 5 parameters, no annotations, and no output schema, the description is incomplete. It doesn't explain what a 'project' is in this system, how it relates to other entities (e.g., organizations, tasks), or what the tool returns. For a mutation tool with rich context, this minimal description leaves critical gaps.

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?

Schema description coverage is 100%, with all 5 parameters well-documented in the schema (e.g., 'Project budget', 'Start date (YYYY-MM-DD)'). The description adds no parameter information beyond what the schema provides. According to rules, with high schema coverage (>80%), the baseline is 3 even with no param info in the description.

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 'Create a new project' clearly states the verb ('create') and resource ('project'), but it's vague about what a 'project' entails in this context and doesn't distinguish it from sibling tools like 'create_task' or 'create_service'. It provides basic purpose but lacks specificity about the domain or 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 offers no guidance on when to use this tool versus alternatives. With many sibling tools like 'create_task', 'create_service', and 'update_project', there's no indication of context, prerequisites, or exclusions. It's a generic statement with no usage instructions.

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