Conecto

Create a task

tasks_create

A new task in a project, numbered like WEB-13. Starts in the project's first "to do" status unless status says otherwise. Link it to a CRM contact, company or deal, or make it a subtask with parent. Costs $0.01 per call; nothing if it fails.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "project": "<project>",
      "title": "<title>"
    },
    "name": "tasks_create"
  }
}

Input Schema

Name	Required	Description
`title`	Yes
`labels`	No
`parent`	No	The task this is a subtask of, like "WEB-4".
`status`	No	One of the project's statuses, e.g. "In progress".
`deal_id`	No
`project`	Yes	A project's key ("WEB") or name.
`assignee`	No	A bot's name or a person's email; "" to clear.
`due_date`	No	YYYY-MM-DD, or null.
`priority`	No
`company_id`	No
`contact_id`	No
`description`	No	Markdown.

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 28, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations declare it is a non-read-only, non-idempotent write, and the description adds real context beyond that: per-call cost of $0.01, waived on failure, and the default-status behavior of the created record. It stops short of saying what is returned or whether duplicate titles are allowed.

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?

Three short sentences, front-loaded with the resource and identifier format, then defaults, then optional relationships, then cost. No sentence is redundant.

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 12-param creation tool with no output schema, the description covers the non-obvious behavior (default status, subtask parent, CRM links, cost). Minor gap: it never indicates what a successful call returns, though the WEB-13 example hints at the identifier.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With only 50% schema description coverage, the description does meaningful work: it explains parent (subtask), status defaulting, and covers the entirely undocumented contact_id/company_id/deal_id by describing CRM linking. Remaining params (title, labels, assignee, due_date, priority) are self-evident from names, enum, and pattern.

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 plus concrete scope: a new task in a project, with an example identifier format (WEB-13), optional CRM linkage and optional subtask parent. It does not, however, distinguish this from the sibling crm_create_task, which an agent could reasonably confuse with it.

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

Usage Guidelines3/5

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

Gives useful creation-time guidance (default status is the project's first 'to do' unless status overrides it; use parent to make a subtask). No when-not-to-use or explicit alternative is named, so the overlap with crm_create_task is left unresolved.

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

All Conecto tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?