Skip to main content
Glama

growthintel-mcp

Pipeline Overview Tool

pipeline-overview-tool
Read-onlyIdempotent

Returns the count of the authenticated tenant's leads grouped by status, source, or budget_tier — e.g. how many leads are 'new' vs 'qualified' vs 'won'. Aggregate counts only, never individual lead records.

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-overview-tool"
  }
}

Input Schema

NameRequiredDescriptionDefault
group_byNoDimension to group lead counts by: status, source, or budget_tier.status

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and idempotentHint, so safety is covered. The description adds meaningful context beyond that: results are scoped to the authenticated tenant and are counts only, never records — which tells the agent what it will and won't get back.

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?

Two sentences, no waste, with the core behavior front-loaded and the key limitation (aggregate only) placed immediately after. Every clause earns its place.

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 one-optional-parameter read tool with annotations and no output schema, the description covers scope, output nature, and grouping well. Only the exact response shape (e.g. mapping of group value to count) is left unstated, which is a minor gap.

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 the single parameter already enumerates status, source, and budget_tier, so the description's mention of those same values adds little. The worked example ('new' vs 'qualified' vs 'won') slightly clarifies intent but is not new semantics. Baseline 3 applies when the schema does the heavy lifting.

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 ('Returns the count of ... leads') plus the grouping dimension, and contrasts itself against record-level tools with 'Aggregate counts only, never individual lead records.' It doesn't name search-leads-tool explicitly, but the contrast makes the distinction clear enough for selection.

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?

Usage is implied: reach for this when you want aggregate counts rather than individual leads, and the 'never individual lead records' clause gestures at the alternative. There is no explicit when-to-use or when-not-to-use routing to a named sibling, so the agent must infer it.

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.

Resources