Dotloop MCP

dotloop_get_recent_activity

Retrieve recent activity for a Dotloop loop by profile and loop ID, with optional limit on entries.

Instructions

Get recent Dotloop loop activity.

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_recent_activity"
  }
}

Input Schema

Name	Required	Description	Default
`limit`	No
`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.2/5.0

Behavior2/5

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

No annotations provided, so the description must fully convey behavioral traits. It claims to get 'recent' activity but does not define recency (e.g., time window, ordering), disclose whether it is read-only, or mention any side effects, rate limits, or authorization requirements.

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 a single sentence, making it concise, but it sacrifices necessary detail. It is front-loaded but does not add enough value to compensate for missing information.

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 3 parameters, no schema descriptions, no annotations, and 24 sibling tools, the description is too vague to uniquely identify the tool's purpose and usage. It fails to cover what the output schema returns or how parameters affect results.

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?

Schema description coverage is 0% with 3 parameters (limit, loop_id, profile_id). The description does not explain any parameter, leaving the agent to infer meanings from names alone, which is insufficient for correct invocation.

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?

The description states 'Get recent Dotloop loop activity' which is a clear verb+resource combination, but it lacks specificity about what type of activity (e.g., tasks, document actions, status changes) and does not differentiate from siblings like dotloop_get_activity_by_type or dotloop_list_loop_activity.

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 such as dotloop_get_activity_by_type or dotloop_list_loop_activity. There is no mention of prerequisites, limitations, or scenarios where this tool is preferred.

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

Deploy Server