Skip to main content
Glama
LeadFlow MCP

LeadFlow MCP

by kfairy9999

Pipeline summary

pipeline_summary
Read-onlyIdempotent

Summarizes lead pipeline health by stage, open value, win rate, and stale leads to reveal follow-up gaps and conversion performance.

Instructions

Counts by stage, open pipeline value in cents, win rate among closed leads (won / (won + lost)), and open leads with no activity for staleAfterDays (default 7). Win rate is null when nothing has closed.

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": "pipeline_summary"
  }
}

Input Schema

NameRequiredDescriptionDefault
asOfNo
staleAfterDaysNoOpen leads with no activity for this many days are stale. Default 7.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is covered. The description adds useful non-schema context: pipeline value is in cents, and win rate is null when nothing has closed, which is a real edge-case disclosure. It does not say what the counts are scoped to (all leads vs. a date window) or what asOf changes.

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?

A single dense sentence with no filler, front-loaded with the highest-value outputs. The parenthetical formula and default clause are compact, though the run-on comma list makes it slightly harder to scan than a short bulleted breakdown would.

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

Completeness4/5

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

With no output schema, the description does the work of enumerating what comes back, including the null win-rate case, which is exactly what an agent needs before calling. The main hole is asOf, whose effect on the results is unstated for a tool that appears to snapshot pipeline state.

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 coverage is only 50%; staleAfterDays is already documented in the schema (including the default 7), so the description's restatement adds little. The asOf parameter is completely unexplained in both schema and description, which matters for a point-in-time snapshot summary.

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 names the four concrete outputs (stage counts, open pipeline value in cents, win rate formula, stale open leads), which makes it unambiguous that this is an aggregate reporting tool rather than a lead CRUD operation like its siblings. There is no leading verb such as 'Compute' or 'Get', so the purpose is implied by the enumerated metrics rather than stated outright.

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?

It never says when to reach for this summary versus search_leads or export_leads_csv, and gives no prerequisites or exclusions. The agent must infer from the name and metric list that this is a read-only dashboard-style call.

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