Agile CRM MCP Server and API by Cotlet

Create task in Agile CRM

agile_crm_create_task

Read-onlyIdempotent

Create task in the user's own Agile CRM account from ChatGPT, Claude or any AI agent. Returns how to do it in Agile CRM step by step (screens, buttons, fields) and opens nothing by itself; then do it with the cotlet_browser_* tools in the user's Agile CRM Cloud Browser. Agile CRM's official API: Yes, Agile CRM has a REST API on all plans, with a daily call cap by plan and no official MCP server (checked 22 Oct 2026).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "agile_crm_create_task"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 9, 2026

TDQS

A3.7/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, and the description corroborates them by stating it "opens nothing by itself," which resolves the tension created by the "create" name. It also adds useful surrounding context (no official MCP server, browser automation required, an API call cap by plan), though it omits what the guidance output actually looks like in structure.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is compact at three sentences, but the opening clause misdirects before the real behavior is disclosed, which is a structural ordering flaw. The closing API verification sentence ("checked 22 Oct 2026") is marginal background that dilutes the core instruction.

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 zero-parameter, no-output-schema tool, the description covers the essentials: what is returned (step-by-step screens, buttons, fields), what is not done (no side effects), and the follow-up tool family to use. Only the shape of the returned guidance and any expected failure modes are left implicit.

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?

The tool takes zero parameters, so there is nothing the description needs to disambiguate beyond the empty schema. Baseline for a 0-parameter tool applies, with no parameter-related confusion introduced.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

"Create task in the user's own Agile CRM account" is front-loaded and implies the tool performs the creation, but the second sentence reveals it only returns step-by-step instructions (screens, buttons, fields) and mutates nothing. The true purpose is stated, but only after a misleading opening that an agent skimming the first clause would misread.

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?

It gives concrete routing guidance: this tool yields guidance, then the agent should execute it with the cotlet_browser_* tools in the user's Agile CRM Cloud Browser. It stops short of naming when to prefer an alternative for the same outcome, but the workflow hand-off is explicit.

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

All Agile CRM MCP Server and API by Cotlet 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?