Skip to main content
Glama

ADS Beast

lead_pipeline_stats

Read-only

Return aggregate lead counts by pipeline stage over a recent window, for the whole organization or for one client.

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

Input Schema

NameRequiredDescriptionDefault
daysNoLength of the window in days, counted back from now. At most one year.
client_idNoRestrict to one client.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds that results are aggregated by stage over a bounded window, but says nothing about data freshness, whether zero-count stages appear, or how large organizations are handled.

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

Conciseness5/5

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

A single sentence with zero filler, front-loading the output (aggregate counts by stage) before the window and scope qualifiers. Nothing could be removed without losing meaning.

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?

For a two-optional-parameter read-only aggregation with no output schema, the description covers what is returned, over what period, and at what scope. Only minor details (stage enumeration, treatment of empty stages) are left implicit.

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 coverage is 100% and both parameters are fully documented in the schema, including the 1-365 day bound and the default of 30. The description's 'recent window' and 'one client' merely restate what the schema already says, adding no new semantics.

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?

States a specific verb and resource: 'Return aggregate lead counts by pipeline stage,' plus the scope ('whole organization or one client'). An agent can tell this is an aggregation/reporting tool rather than a per-lead lookup like get_lead, though no sibling is named explicitly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The scope clause ('whole organization or for one client') implies when to pass client_id versus omit it, which is useful selection guidance. However, there is no explicit when-to-use/when-not framing and no routing to alternatives such as analytics_summary or other reporting tools.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.