Skip to main content
Glama
dragosroua

addTaskManager MCP Server

by dragosroua

assess_edit_idea

Edit idea content within the Assess realm to update task or project concepts before moving to planning stages.

Instructions

Edit idea content in Assess realm.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
ideaRecordNameYesRecord name of the idea to edit
ideaNameNoUpdated idea name

Implementation Reference

  • The primary handler function implementing the 'assess_edit_idea' tool logic. It takes the idea record name and new name, and returns a mock success response indicating the idea has been updated.
    private async editIdea(ideaRecordName: string, ideaName: string) {
      // Mock idea edit via CloudKit
      return { content: [{ type: 'text', text: `Idea ${ideaRecordName} updated with name: ${ideaName}` }] };
    }
  • The input schema definition for the 'assess_edit_idea' tool, specifying the required ideaRecordName and optional ideaName parameters.
    inputSchema: {
      type: 'object',
      properties: {
        ideaRecordName: { type: 'string', description: 'Record name of the idea to edit' },
        ideaName: { type: 'string', description: 'Updated idea name' }
      },
      required: ['ideaRecordName']
    }
  • src/index.ts:341-352 (registration)
    Registration of the 'assess_edit_idea' tool in the listTools response, including name, description, and schema.
    {
      name: 'assess_edit_idea',
      description: 'Edit idea content in Assess realm.',
      inputSchema: {
        type: 'object',
        properties: {
          ideaRecordName: { type: 'string', description: 'Record name of the idea to edit' },
          ideaName: { type: 'string', description: 'Updated idea name' }
        },
        required: ['ideaRecordName']
      }
    },
  • src/index.ts:675-677 (registration)
    The switch case in the CallToolRequestHandler that routes calls to 'assess_edit_idea' to the editIdea handler method.
      this.validateArgs(args, ['ideaRecordName']);
      return await this.editIdea(args.ideaRecordName, args.ideaName);
    case 'assess_create_collection':
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 edits idea content, implying a mutation operation, but doesn't disclose critical traits like required permissions, whether changes are reversible, rate limits, or what happens to unspecified fields. For a mutation 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.

Conciseness4/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 ('Edit idea content') and domain ('Assess realm'). It avoids unnecessary words and gets straight to the point. However, it could be slightly more structured by explicitly listing editable fields or usage context, but it earns high marks for brevity and clarity within its limited scope.

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 mutation tool with no annotations and no output schema, the description is incomplete. It lacks details on behavioral traits (e.g., permissions, side effects), doesn't explain return values or error handling, and offers minimal guidance. While the schema covers parameters well, the overall context for safe and effective use is insufficient, especially compared to siblings that might have overlapping functionalities.

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 clear descriptions for both parameters: 'ideaRecordName' (record name of the idea to edit) and 'ideaName' (updated idea name). The description adds no additional meaning beyond the schema, such as format examples or constraints. Given the high schema coverage, a baseline score of 3 is appropriate, as the schema adequately documents parameters without extra help from 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 states the action ('Edit idea content') and domain ('Assess realm'), which clarifies the basic purpose. However, it's vague about what 'content' entails (e.g., name, description, status) and doesn't differentiate from siblings like 'assess_edit_project' or 'assess_edit_task' beyond specifying 'idea' as the resource. It avoids tautology by not restating the name/title 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?

No explicit guidance on when to use this tool versus alternatives is provided. The description implies usage for editing ideas in the Assess realm, but it doesn't mention prerequisites (e.g., existing ideas), exclusions, or comparisons to siblings like 'assess_create_idea' or 'assess_archive_task_to_collection'. Without such context, users must infer usage from the tool name 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/dragosroua/addtaskmanager-mcp-server'

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