Skip to main content
Glama
Sign In
Kommo CRM MCP Server

Kommo CRM MCP Server

by Miguelgbastos
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

get_tasks

Retrieve a list of tasks from Kommo CRM with pagination and customizable limits to streamline task management and workflow efficiency.

Instructions

Get list of tasks from Kommo CRM

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": "get_tasks"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoNumber of tasks to return (max 250)
pageNoPage number for pagination

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.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 of behavioral disclosure. It only states the basic action ('Get list of tasks') without mentioning permissions, rate limits, pagination behavior (implied by parameters but not explained), or what the returned list includes. This is inadequate for a tool with parameters and no output schema.

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 a single, efficient sentence with no wasted words. It's front-loaded with the core purpose, making it easy to scan and understand quickly.

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?

Given the lack of annotations and output schema, the description is incomplete. It doesn't explain the tool's behavior, return format, or how it differs from siblings, leaving significant gaps for an agent to use it effectively in a CRM context with multiple similar retrieval tools.

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 description coverage is 100%, with clear descriptions for 'limit' and 'page' parameters. The description adds no additional parameter semantics beyond what the schema provides, so it meets the baseline score of 3 without compensating or detracting.

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 clearly states the verb ('Get') and resource ('list of tasks from Kommo CRM'), making the purpose understandable. However, it doesn't distinguish this tool from other 'get_' siblings like get_contacts or get_leads, which follow a similar pattern but target different resources.

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?

The description provides no guidance on when to use this tool versus alternatives. With many sibling tools (e.g., get_contacts, get_leads), there's no indication of whether this is for general task retrieval or specific contexts, leaving the agent to infer usage from the name alone.

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

Related Tools