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.7/5.0
Behavior2/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries full responsibility for behavioral disclosure. 'Create a new task' only restates the action; it does not mention side effects, authentication needs, response format, or potential risks, which is a significant gap for a mutation tool.
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, direct sentence with no wasted words. It is perfectly concise and front-loaded, though it sacrifices completeness for brevity.
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 four parameters, no output schema, no annotations, and a rich set of sibling tools, the description is far from complete. It omits return value information, any usage context, and parameter semantics, making it inadequate for confident tool invocation.
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%, and the tool description provides no parameter information at all. It fails to compensate for the low schema coverage, leaving title, priority, and description parameters entirely unexplained beyond basic types and enum values.
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 'Create a new task' states a clear verb and resource, unambiguously indicating the tool's function. It does not explicitly distinguish from sibling tools like update_task or delete_task, but the resource and action are distinct enough for basic selection.
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 such as update_task or list_tasks. The description lacks context about prerequisites, typical scenarios, or exclusions, leaving the agent without decision support.
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.2/5.0
Disambiguation4/5
Most tools target distinct resources and actions, but a few pairs (check_email_spam_score vs check_step_spam_score, get_deliverability vs check_domain_deliverability) have overlapping concerns. However, descriptions clarify the differences, so an agent can distinguish them with careful reading.
Naming Consistency5/5
All tools follow a consistent verb_noun pattern with lowercase snake_case. The use of add vs create is a minor style variation but does not create confusion.
Tool Count2/5
At 34 tools, the server exceeds the typical 3-15 tool range and even the 16-25 heavy range. While the broad functionality justifies many tools, the count is likely to make tool selection more difficult for an agent.
Completeness4/5
The tool set covers the full campaign lifecycle including creation, scheduling, processing, and deliverability tracking, plus contact and provider management. Notable gaps include no update_contact or get_campaign by ID, but these are workarounds via list operations.