Skip to main content
Glama

list_prospects

Read-only

List the coach's prospects (leads who have not become clients yet). Optionally filter by status.

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

Input Schema

NameRequiredDescriptionDefault
statusNo
pageSizeNo
pageNumberNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.1/5.0
Behavior2/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. Beyond that the description adds only the domain definition of a prospect; it says nothing about pagination behavior despite pageSize defaulting to 50 and pageNumber existing, nothing about result ordering, and nothing about what happens with large prospect sets.

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 short sentences, the resource definition is front-loaded, and the optional filter is stated second. There is no filler or redundancy.

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?

For a simple read-only list with no output schema, the definition is minimally adequate but leaves gaps an agent must guess at: pagination defaults and limits, sort order, and the meaning of the status enum, particularly why CONVERTED or NOT_INTERESTED would appear under a prospect listing.

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 description coverage is 0%, so the description carries the burden and largely fails it: it mentions the status filter but never explains the enum values (notably the distinction between HOT and WARM, or CONVERTED appearing in a 'not yet clients' list), and never mentions pageSize or pageNumber at all.

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 ('List') and resource ('prospects'), and the parenthetical '(leads who have not become clients yet)' disambiguates it from list_clients, which is the most likely confusion in this catalog. It stops short of naming siblings explicitly, so 4 rather than 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?

'Optionally filter by status' implies the calling pattern but gives no when-to-use framing, no guidance on when to paginate versus request a full list, and no indication of ordering or whether the result is coach-scoped only. Usage is inferable from the name but not stated.

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.