Skip to main content
Glama
Sign In
Dotloop MCP

Dotloop MCP

by theperrygroup
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

dotloop_get_all_tasks_in_loop

Retrieve all tasks associated with a specific loop in Dotloop to view progress and assignments.

Instructions

Get all 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_all_tasks_in_loop"
  }
}

Input Schema

NameRequiredDescriptionDefault
loop_idYes
profile_idYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.7/5.0
Behavior2/5

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

With no annotations, the description must disclose behavioral traits. It only says 'Get all tasks', implying read-only but provides no details on idempotency, safety, or side effects. No mention of pagination or result structure.

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

Conciseness4/5

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

The description is a single concise sentence. It could be slightly more structured but is appropriately short for a simple query tool.

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?

Despite having an output schema, the description lacks context about required parameters and does not clarify how this tool relates to other task-list tools. Incomplete for effective agent usage.

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?

Schema description coverage is 0%, and the tool description adds no meaning to the parameters loop_id and profile_id. An agent cannot infer what these identifiers mean or where to find them.

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 'Get all tasks in a Dotloop loop' clearly states the verb and resource. However, it does not differentiate from sibling tools like dotloop_get_task, dotloop_list_tasks, or dotloop_get_completed_tasks, which also deal with 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 on when to use this tool versus alternatives. No mention of prerequisites or context for using dotloop_get_all_tasks_in_loop among many task-related siblings.

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