Skip to main content
Glama
daanno

Simplicate MCP Server

by daanno

get_tasks

Retrieve project tasks from Simplicate business data with configurable limits and offsets for efficient task management.

Instructions

Retrieve project tasks

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMaximum number to return
offsetNoNumber to skip

Implementation Reference

  • MCP server handler for the 'get_tasks' tool. Extracts parameters and delegates execution to SimplicateService.getTasks, then formats response.
    case 'get_tasks': {
      const data = await this.simplicateService.getTasks({
        limit: (toolArgs.limit as number) || 10,
        offset: (toolArgs.offset as number) || 0,
      });
      return { content: [{ type: 'text', text: JSON.stringify(data, null, 2) }] };
  • Tool registration entry in listTools handler, defining name, description, and input schema for 'get_tasks'.
      name: 'get_tasks',
      description: 'Retrieve project tasks',
      inputSchema: {
        type: 'object',
        properties: {
          limit: { type: 'number', description: 'Maximum number to return' },
          offset: { type: 'number', description: 'Number to skip' },
        },
      },
    },
  • Input schema definition for the 'get_tasks' tool.
      inputSchema: {
        type: 'object',
        properties: {
          limit: { type: 'number', description: 'Maximum number to return' },
          offset: { type: 'number', description: 'Number to skip' },
        },
      },
    },
  • Actual API service method implementing getTasks logic, fetching from Simplicate API endpoint '/projects/task' with project_id requirement.
    async getTasks(params?: { limit?: number; offset?: number; project_id?: string }): Promise<SimplicateTask[]> {
      // Note: Tasks endpoint requires project_id filter in Simplicate
      // Without project_id, this will return empty array
      if (!params?.project_id) {
        console.warn('getTasks: project_id is required but not provided, returning empty array');
        return [];
      }
      try {
        const response = await this.client.get('/projects/task', params);
        return response.data || [];
      } catch (error) {
        console.error('getTasks: endpoint may not be available or requires different parameters');
        return [];
      }
    }
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. 'Retrieve' implies a read operation, but it doesn't disclose behavioral traits like pagination (implied by limit/offset parameters), authentication needs, rate limits, error conditions, or what happens when no tasks exist. The description is minimal and lacks essential operational context.

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 just two words, with zero wasted text. It's front-loaded with the core purpose, though this brevity comes at the cost of completeness. Every word earns its place by directly stating the tool's function.

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 task retrieval tool with 2 parameters, no annotations, and no output schema, the description is incomplete. It doesn't explain what 'project tasks' means, how results are returned, or any behavioral aspects, leaving significant gaps for the agent to infer.

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 both parameters (limit and offset) well-documented in the schema. The description adds no parameter information beyond what's in the schema, so it meets the baseline of 3 for high schema coverage without compensating value.

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 'Retrieve project tasks' clearly states the verb (retrieve) and resource (project tasks), but it's vague about scope and doesn't distinguish from sibling tools like 'get_task' (singular) or 'search'. It doesn't specify whether this retrieves all tasks, tasks for specific projects, or tasks with certain filters.

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 about when to use this tool versus alternatives like 'get_task' (singular), 'search', or 'get_projects'. The description doesn't mention prerequisites, context, or exclusions, leaving the agent to guess based on tool names alone.

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