Pipedrive MCP Server

get_quarterly_progress

Track current quarter sales progress with forecasting data and date awareness in Pipedrive CRM. Retrieve deal probability-based forecasts and filter by user to monitor performance.

Instructions

Get progress tracking for current quarter with forecasting data and date awareness

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

Input Schema

Name	Required	Description	Default
`user_id`	No	Filter by specific user (optional)
`include_forecast`	No	Include deal probability-based forecasting (default: true)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Apr 1, 2026

TDQS

C2.9/5.0

Behavior3/5

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

With no annotations provided, the description carries the full burden. It discloses 'forecasting data' (indicating deal probability calculations) and 'date awareness' (implying automatic current quarter detection), but omits safety information (read-only status), side effects, or rate limits.

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?

Single sentence, front-loaded with the action verb. While efficient, 'date awareness' is vague and could be replaced with more specific behavioral context. No redundant phrases.

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

Completeness3/5

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

With no output schema and no annotations, the description should better explain what 'progress tracking' returns (metrics, deals, summary?). It mentions key features (forecasting, quarterly scope) but leaves the actual return structure undefined.

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%, establishing a baseline of 3. The description mentions 'forecasting data' which aligns with the include_forecast parameter, and 'current quarter' hints at implicit date filtering not shown in the schema, but adds no syntax, format, or dependency details beyond the schema.

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 the tool gets 'progress tracking' for the 'current quarter' with 'forecasting data,' which provides some scope, but 'progress tracking' remains vague and fails to distinguish from siblings like get_quarter_summary or get_current_quarter_deals. The verb 'Get' is generic.

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 like get_quarter_summary, get_overview, or get_current_quarter_deals. There are no exclusions, prerequisites, or workflow positioning hints.

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