Skip to main content
Glama

MedaRep

My prospect lists

my_lists
Read-onlyIdempotent

The rep's prospect lists on MedaRep with counts by status, or one list (by id or name) with where each surgeon stands (target, contacted, trialing, using_us, competitor, lost, passed: the account's own stage, the same on every list), note, practice and latest Medicare cases.

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

Input Schema

NameRequiredDescriptionDefault
listNoA list id or name; omit for all lists.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so the safety profile is covered. The description adds genuinely useful behavior beyond that: what the summary mode returns (counts by status), what the detail mode returns (stage, note, practice, latest Medicare cases), and the non-obvious rule that stage is the account's own stage and identical across every list.

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?

It is one sentence that front-loads the summary mode and then the detail mode, with no filler. The deeply nested parenthetical listing the seven stage values is dense and slows parsing, but every clause carries information.

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 read-only tool with one optional parameter, no output schema, and full schema coverage, the description is nearly sufficient because it enumerates the returned fields and explains the stage semantics. It stops short on pagination, list-size limits, and ordering, which matters for a tool that may return many lists or many surgeons.

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 documents 'A list id or name; omit for all lists.' The description restates that meaning without adding resolution behavior (e.g., what happens on an ambiguous name match or an unknown id), so the baseline 3 applies.

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 a specific resource (the rep's prospect lists on MedaRep) and two distinct modes: all lists with counts by status, or a single list with per-surgeon detail. That is enough for an agent to know what it retrieves, though it never contrasts itself with nearby read tools like my_accounts or my_customers.

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 through the optional 'list' argument ('omit for all lists'), which tells the agent how to switch modes but not when this tool is preferable to sibling list/account tools. No exclusions or prerequisites are 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.

Resources