Skip to main content
Glama

accelo_create_task

Create a new Accelo task on a job, milestone, or issue with title, start date, assignee, due date, and priority to track work items.

Instructions

Create a new task.

Args: title: Task title (required) against_type: Object type (required) — e.g. job, milestone, issue against_id: Object ID (required) date_started: Start date as unix timestamp (required) description: Task description assignee_id: Staff ID to assign manager_id: Staff ID for manager date_due: Due date (unix timestamp) priority_id: Priority ID status_id: Initial status ID remaining: Budgeted time remaining in seconds fields: Additional fields to return

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
titleYes
fieldsNo
date_dueNo
remainingNo
status_idNo
against_idYes
manager_idNo
assignee_idNo
descriptionNo
priority_idNo
against_typeYes
date_startedYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
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. It implies a mutation but never states required permissions, what happens on an invalid against_type/against_id, whether the new task ID is returned, or any side effects — significant gaps for a create operation.

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?

Purpose is front-loaded in the first sentence and the rest is a clean, zero-waste argument list. Appropriately sized for a 12-parameter tool.

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?

For a 12-parameter mutation tool with no annotations, no output schema, and 0% schema description coverage, the description covers only the arguments. It omits behavior, permissions, and return/error information an agent needs to invoke it correctly, leaving the definition materially incomplete.

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 coverage is 0%, so the description must compensate, and it does document all 12 parameters with some added meaning: against_type examples (job, milestone, issue), unix-timestamp format for dates, and seconds for remaining. However the semantics remain thin (against_id is just "Object ID", assignee/manager IDs are unexplained) and no parameter is described in depth, so it only partially compensates.

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?

States a specific verb and resource ("Create a new task"), which is enough to distinguish it from the list_tasks/get_task/update_task/delete_task siblings. It stops short of explicitly naming or contrasting with those alternatives, so it lands at a clear-but-undifferentiated 4.

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?

There is no when-to-use guidance, no prerequisites, and no mention of alternatives. The body is purely an argument list, so an agent gets no routing help beyond the name.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools