Skip to main content
Glama

get_prospect_stats

Read-only

Counts of prospects by pipeline stage (new / contacted / hot / warm / did not pick up / converted / not interested / low budget / out of radius / legacy lost) for the coach.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

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 and openWorldHint=false, so safety is covered. The description's real contribution is enumerating the ten pipeline buckets, which substitutes for a missing output schema, but it says nothing about scope or time window (current snapshot vs. historical, per-coach vs. all prospects), leaving aggregation semantics unclear.

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 front-loaded sentence with the verb and grouping stated first. The long stage enumeration is verbose but earns its place because no output schema exists to document the buckets.

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 parameterless read-only stats tool, the definition tells the agent what the result contains, which is the main thing needed. Remaining gaps are scope-related (whose prospects, what time frame) rather than structural.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool has zero parameters, so by the baseline rule this scores 4. There is nothing for the description to compensate for on the input side.

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 states a specific verb+resource (counts of prospects) and adds the grouping dimension (by pipeline stage), so an agent knows exactly what the tool returns. It does not explicitly differentiate itself from the sibling get_coach_dashboard_stats, which prevents a 5.

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 only implied: an agent can infer this is the tool for prospect pipeline numbers, and 'for the coach' hints at the dashboard context. There is no explicit when-to-use or when-not-to-use guidance, and no pointer to the dashboard-stats sibling that likely overlaps.

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.