Dotloop MCP

dotloop_get_completed_tasks

Retrieve completed tasks from a Dotloop loop using profile and loop IDs to access task status.

Instructions

Get completed tasks in a Dotloop loop.

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": {
      "profile_id": "<profile_id>",
      "loop_id": "<loop_id>"
    },
    "name": "dotloop_get_completed_tasks"
  }
}

Input Schema

Name	Required	Description	Default
`loop_id`	Yes
`profile_id`	Yes

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jun 27, 2026

TDQS

C2.5/5.0

Behavior2/5

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

With no annotations, the description carries full burden but only states 'Get completed tasks.' It does not disclose whether the operation is read-only, the side effects, or behavior when no tasks exist. The read-only nature is implied but not explicit.

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

Conciseness2/5

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

The description is extremely terse—one sentence—but under-specifies the tool. While there is no wasted text, the lack of necessary detail makes it inadequate, not concisely effective.

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

Completeness1/5

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

Despite having an output schema, the description omits any detail about the return format, prerequisites (e.g., valid profile/loop IDs), error handling, or what constitutes a 'completed task.' This is insufficient for a tool with zero schema description coverage and no annotations.

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

Parameters1/5

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

The parameter schema has 0% description coverage, and the tool description does not explain the purpose of 'profile_id' or 'loop_id.' The agent receives no additional meaning beyond parameter names and types.

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 clearly states the verb 'Get', the resource 'completed tasks', and the scope 'in a Dotloop loop.' This distinguishes it from sibling tools like dotloop_get_all_tasks_in_loop and dotloop_get_pending_tasks.

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 such as dotloop_get_all_tasks_in_loop or dotloop_list_tasks. The description does not mention context or exclusion criteria.

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

Deploy Server