Bitrix24 MCP server

b24_tasks_complete

Marks a task as completed in Bitrix24. Provide the task ID to update its status.

Instructions

Marca una tarea como completada.

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": {
      "id": "<id>"
    },
    "name": "b24_tasks_complete"
  }
}

Input Schema

Name	Required	Description	Default
`id`	Yes	ID de la tarea a completar
`webhook_url`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv2.0.0May 11, 2026

TDQS

C2.6/5.0

Behavior2/5

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

No behavioral details beyond the action are disclosed. Important traits like idempotency, side effects (notifications), or required permissions are omitted. Since annotations are absent, the description should carry the burden, but fails to do so.

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?

The description is very short (5 words), which is concise but missing necessary context. It is front-loaded but not sufficiently informative for an autonomous agent.

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 does not address error cases, expected outcomes, or distinctions from similar tools. A more detailed description is needed for reliable tool selection.

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

Parameters2/5

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

Only 50% of parameters have descriptions in the schema. The description adds no extra meaning for 'id' and does not explain the purpose of 'webhook_url'. The schema's coverage is partial, and the description does not 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 clearly states the action ('completar' - complete) and the resource ('tarea' - task). It is specific enough to distinguish from generic update tools like b24_tasks_update.

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 (e.g., b24_tasks_update for other status changes). No prerequisites or exclusions are mentioned.

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