Skip to main content
Glama
dragosroua

addTaskManager MCP Server

by dragosroua

assess_create_context

Create a new context in the Assess realm for organizing tasks and projects within the ADD framework, enabling structured task management.

Instructions

Create a new context in Assess realm.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
contextNameYesContext name (max 30 chars)

Implementation Reference

  • src/index.ts:318-328 (registration)
    Tool registration in the ListToolsRequestSchema handler, including name, description, and input schema.
    {
      name: 'assess_create_context',
      description: 'Create a new context in Assess realm.',
      inputSchema: {
        type: 'object',
        properties: {
          contextName: { type: 'string', description: 'Context name (max 30 chars)' }
        },
        required: ['contextName']
      }
    },
  • src/index.ts:680-682 (registration)
    Tool registration in the CallToolRequestSchema switch statement, dispatching to the createContext handler.
    case 'assess_create_context':
      this.validateArgs(args, ['contextName']);
      return await this.createContext(args.contextName);
  • The main handler function that implements the tool logic. Generates a unique mock CloudKit recordName and returns a success response.
    private async createContext(contextName: string) {
      const recordName = `context_${uuidv4()}`;
      // Mock context creation via CloudKit
      return { content: [{ type: 'text', text: `Context "${contextName}" created with recordName: ${recordName}` }] };
    }
  • TypeScript interface defining the structure of a ZenTaskticContext record, used for CloudKit data modeling.
    interface ZenTaskticContext {
      recordName?: string;
      recordType: 'Contexts';
      fields: {
        contextName: { value: string }; // Max 30 chars, min 1
        uniqueId: { value: string }; // UUID
        lastModified: { value: number }; // Timestamp
        
        // References (relationships in Core Data)
        projects?: { value: CKReference[] }; // List of references to Project records
        tasks?: { value: CKReference[] }; // List of references to Task records
      };
    }
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. While 'Create' implies a write operation, the description doesn't specify permissions required, whether this is idempotent, what happens on duplicate names, or what the response includes. For a mutation 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 a single, efficient sentence with no wasted words. It's front-loaded with the core action and resource, making it easy to parse quickly. Every word earns its place by conveying essential information without redundancy.

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 tool creates a new resource (a mutation) with no annotations and no output schema, the description is incomplete. It doesn't explain what a 'context' is, how it fits into the Assess realm, what happens after creation, or any error conditions. For a creation tool in a system with many sibling tools, more context is needed to guide proper usage.

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 input schema has 100% description coverage, with the single parameter 'contextName' documented as 'Context name (max 30 chars)'. The description adds no additional parameter semantics beyond what's in the schema, such as naming conventions or examples. With high schema coverage, a baseline score of 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.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the action ('Create') and resource ('new context in Assess realm'), making the purpose understandable. However, it doesn't differentiate this tool from similar creation tools like 'assess_create_collection', 'assess_create_idea', 'assess_create_project', and 'assess_create_task' that also create resources in the Assess realm, which prevents a perfect score.

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 explain what a 'context' is in the Assess realm, how it differs from other resources like collections or projects, or when to choose this over other creation tools. This leaves the agent with minimal context for appropriate selection.

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