create_task
Create a new task
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| title | Yes | ||
| dueDate | No | ISO date (optional) | |
| priority | No | ||
| description | No |
Mailcannon
TDQS
C2.3/5.0
Behavior1/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations exist, so the description carries full burden for behavioral disclosure. It only states 'Create a new task' without any details on idempotency, side effects, authorization needs, or error conditions, similar to the LOW calibration example.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness2/5
Is the description appropriately sized, front-loaded, and free of redundancy?
At four words, the description is extremely terse. While concise, it is under-specified and lacks necessary context, making it insufficient for an AI agent to understand the tool's full functionality.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness1/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given four parameters with low schema coverage, no output schema, and no annotations, the description is entirely inadequate. It provides no return value information, no preconditions, and no clarity on behavior, leaving the agent with minimal actionable context.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters1/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is only 25% (only dueDate has a description). The tool description adds no meaning beyond parameter names for title, priority, and description. It fails to clarify formats, constraints, or default values for the three undocumented parameters.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose5/5
Does the description clearly state what the tool does and how it differs from similar tools?
The description 'Create a new task' uses a specific verb and resource, clearly indicating the action and object. It distinguishes from sibling tools like update_task, delete_task, and list_tasks, making the purpose unmistakable.
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 on when to use this tool versus alternatives. With many sibling tools (add_contact, create_campaign, etc.), the description offers no context for appropriate usage or exclusions.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Try in Browser
Glama MCP Gateway
Add one secure layer between your agents and this server.
TDQS
B3.3/5.0
Disambiguation5/5
Each tool targets a distinct action and resource. Campaign lifecycle steps (create, update, delete, schedule, pause, resume) are clearly separate from contact management (add, remove, update tags) and provider/domain operations. No two tools have overlapping purposes.
Naming Consistency5/5
All tools follow a consistent verb_noun pattern with underscores (e.g., add_contact, check_domain_deliverability, delete_campaign_step). Mixing of singular/plural nouns (list_campaigns vs list_tags) is intentional and does not break consistency.
Tool Count4/5
34 tools is high but justified for a full-featured email campaign server covering campaigns, contacts, providers, scheduling, deliverability, and task management. A few tools like check_email_spam_score and check_step_spam_score could be merged, but overall the count is reasonable.
Completeness5/5
The tool surface covers the complete CRM lifecycle: campaign CRUD, step management, contact CRUD with tags, provider setup, scheduling, deliverability checks, and spam analysis. Only minor gaps like per-campaign analytics or import/export exist, but core workflows are fully covered.