Skip to main content
Glama

list_organization_prospects

Read-only

The gym's shared lead pipeline (people who enquired via the gym page or were added by coaches), optionally filtered by status or coach. Use update_prospect_status / add_prospect_note with the returned _id.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "organizationId": "<organizationId>"
    },
    "name": "list_organization_prospects"
  }
}

Input Schema

NameRequiredDescriptionDefault
statusNo
coachIdNo
organizationIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/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 the safety profile is covered. The description adds behavioral context beyond that: prospects come from the gym page or coach additions, and results carry an _id that feeds mutations. It says nothing about ordering, pagination, or result size, which are the behaviors an agent would otherwise have to guess.

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 with zero filler: the first states what the resource is and its filters, the second hands off the returned identifier to the mutation tools. Scope and next step are both front-loaded.

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 annotations covering its safety profile and no output schema, the description is close to sufficient and its mention of the returned _id hints at return content. It still leaves out pagination/ordering behavior and any differentiation from the parallel list_prospects tool, which an agent needs before calling it correctly.

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 description coverage is 0%, so the description must carry parameter meaning. It does explain that status and coach are optional filters, which maps to two of three parameters and implies the enum values are statuses. The required organizationId is never mentioned and no filter format or combination behavior is given, so compensation is only partial.

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 specific resource and its scope: 'The gym's shared lead pipeline (people who enquired via the gym page or were added by coaches)'. It defines what a prospect is, which is more than a restated name. It does not, however, distinguish this from the sibling list_prospects, so an agent cannot tell when the 'organization' scoping matters versus the other list.

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?

It states the optional filters (status or coach) and routes the agent forward by saying to use update_prospect_status / add_prospect_note with the returned _id, which is useful workflow guidance. There is no explicit when-to-use versus list_prospects or any exclusion, so the selection guidance is only implied.

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.