Skip to main content
Glama
kazan-project-manufactory

Aspro Cloud MCP

list_tasks

Filter and list tasks from Aspro Cloud by status, owner, type, or model. Returns active tasks by default; include archived tasks with archive_status.

Instructions

List tasks with optional filters.

By default returns only NON-ARCHIVED tasks (archive_status=0). "Active tasks" and "tasks" always means non-archived. To get archived tasks, pass archive_status=10.

Status values (use 'status' param): 1 = New (created but not started — most tasks accumulate here as backlog) 3 = In Progress (actively being worked on right now) 4 = Waiting Review (done by assignee, pending verification) 5 = Done (completed but not yet archived)

To find tasks truly in progress use status=3. To find all incomplete tasks use status=1, 3, or 4.

Type values: 0=Task, 1=Inbox, 20=Event, 30=Template

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNoPage number for pagination
typeNoType: 0=Task, 1=Inbox, 20=Event, 30=Template
modelNoModel binding (e.g. 'lead')
moduleNoModule binding (e.g. 'crm')
statusNoStatus: 1=New (backlog), 3=In Progress, 4=Waiting Review, 5=Done. Use 3 for 'currently working on'.
model_idNoID of the bound object
owner_idNoFilter by task owner (creator) user ID
parent_idNoFilter by parent task ID
archive_statusNo0=Not archived (default), 10=Archived. Pass 10 to see archived tasks.
responsible_idNoFilter by responsible user ID
Behavior4/5

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

With no annotations, the description carries the full burden. It explains the default non-archived behavior, the meaning of each status value, and how to retrieve archived tasks. It does not discuss pagination or response format, but these are minor gaps for a list 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 well-structured with clear sections for status and type values. It front-loads the main purpose and default behavior, and every sentence provides useful information without redundancy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a tool with 10 optional parameters and no output schema, the description covers the critical semantics: status meaning, type meaning, and archive behavior. It omits pagination details (e.g., page size), but this is not essential for correct invocation.

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 covers all 10 parameters with descriptions (100% coverage), so the baseline is 3. The description adds usage context like 'To find tasks truly in progress use status=3' but largely restates the schema's parameter descriptions rather than adding new semantic depth.

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 starts with 'List tasks with optional filters', providing a clear verb+resource. It distinguishes from sibling tools (get_task, update_task, delete_task) by focusing on listing and further specifies the default non-archived scope.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description gives clear context on when to use filters: explains status values, archive_status behavior, and provides explicit queries for 'truly in progress' and 'all incomplete tasks'. However, it does not name alternative tools or state when not to use this tool, so it stops short of a 5.

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