Skip to main content
Glama
dragosroua

addTaskManager MCP Server

by dragosroua

assess_remove_task_from_idea

Remove a task from an idea in the Assess realm of the addTaskManager app. This tool helps manage task-idea relationships by unlinking specific tasks from ideas during the assessment phase.

Instructions

Remove a task from an idea in Assess realm.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
taskRecordNameYesRecord name of the task
ideaRecordNameYesRecord name of the idea

Implementation Reference

  • The handler function that executes the tool logic. It mocks removing the task reference from the idea record in CloudKit and returns a success message.
    private async removeTaskFromIdea(taskRecordName: string, ideaRecordName: string) {
      // Mock removing task from idea via CloudKit
      return { content: [{ type: 'text', text: `Task ${taskRecordName} removed from idea ${ideaRecordName}` }] };
    }
  • The tool definition including name, description, and input schema for validation, registered in the list of tools.
    {
      name: 'assess_remove_task_from_idea',
      description: 'Remove a task from an idea in Assess realm.',
      inputSchema: {
        type: 'object',
        properties: {
          taskRecordName: { type: 'string', description: 'Record name of the task' },
          ideaRecordName: { type: 'string', description: 'Record name of the idea' }
        },
        required: ['taskRecordName', 'ideaRecordName']
      }
    },
  • src/index.ts:692-694 (registration)
    The dispatch case in the CallToolRequestSchema handler that validates arguments and calls the removeTaskFromIdea method.
    case 'assess_remove_task_from_idea':
      this.validateArgs(args, ['taskRecordName', 'ideaRecordName']);
      return await this.removeTaskFromIdea(args.taskRecordName, args.ideaRecordName);
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 mentions 'Remove' which implies a mutation, but does not disclose behavioral traits such as permissions required, whether the task is deleted or unlinked, side effects, or error handling. This leaves significant gaps for an agent to understand the tool's behavior.

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 sentence that is front-loaded and to the point, with no unnecessary words. However, it could be more structured by including key details like behavioral traits, but given its brevity, it earns a high score for 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 no annotations and no output schema, the description is incomplete for a mutation tool with 2 parameters. It lacks information on what the tool returns, error conditions, or important behavioral context, making it inadequate for an agent to use effectively without additional assumptions.

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%, so the schema already documents both parameters ('taskRecordName' and 'ideaRecordName') adequately. The description does not add any meaning beyond what the schema provides, such as explaining what 'Record name' entails or format examples. Baseline 3 is appropriate as the schema does the heavy lifting.

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 states the action ('Remove') and target resource ('a task from an idea in Assess realm'), which is clear but vague about what 'remove' entails (e.g., unlinking vs. deleting). It distinguishes from some siblings like 'assess_add_task_to_idea' but not clearly from 'assess_remove_task_from_project', which has similar structure but different target resource.

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 explicit guidance on when to use this tool versus alternatives like 'assess_remove_task_from_project' or other task/idea management tools. The description implies usage for removing tasks from ideas in the Assess realm, but lacks context on prerequisites, conditions, or exclusions.

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/dragosroua/addtaskmanager-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server