Skip to main content
Glama
kazan-project-manufactory

Aspro Cloud MCP

create_task

Create tasks in Aspro Cloud CRM, specifying type, status, deadline, priority, and assignment to leads or workflows.

Instructions

Create a new task

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesTask name
typeNoType: 0=Task, 1=Inbox, 20=Event, 30=Template
modelNoModel to bind task to (e.g. 'lead')
moduleNoModule to bind task to (e.g. 'crm')
statusNoStatus: 1=New, 3=In Progress, 4=Waiting Review, 5=Done
deadlineNoDeadline date (YYYY-MM-DD or YYYY-MM-DD HH:MM:SS)
model_idNoID of the object to bind task to
owner_idNoTask owner (creator) user ID
priorityNoPriority level
parent_idNoParent task ID for subtasks
descriptionNoTask description
workflow_idNoWorkflow ID
time_estimateNoEstimated time in seconds
responsible_idNoResponsible user ID
plan_start_dateNoPlanned start date (YYYY-MM-DD)
workflow_stage_idNoWorkflow stage ID
Behavior1/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations provided, the description carries the full burden of disclosing behavioral traits. It only states the action and resource, omitting any details about required fields, side effects, permissions, or response behavior. This is a tautology of the tool name.

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?

The description is extremely short and free of fluff, but it is under-specified rather than appropriately concise. It provides no structure or additional context, similar to a restatement of the tool name, which offers minimal value.

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 the tool has 16 parameters, no output schema, and no annotations, the description is entirely inadequate. It does not explain what a task is, how it relates to other entities, what the creation process entails, or what the response looks like. The description is insufficient for an agent to use the tool effectively.

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 descriptions cover 100% of the parameters, so the baseline is 3 even though the tool description itself adds no parameter information. The schema already documents each parameter's meaning and format, so the description does not need to compensate.

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' uses a specific verb and resource, clearly indicating a creation operation for tasks. It distinguishes from sibling tools like create_lead by naming the resource 'task', though it lacks additional detail about task semantics.

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. It does not mention prerequisites, exclusions, or relationships with other tools like update_task or list_tasks. The description is purely imperative with no context.

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/kazan-project-manufactory/aspo-cloud-mcp'

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