Skip to main content
Glama

MedaRep

Save surgeons to a list

save_to_list

Add surgeons by NPI to one of the rep's prospect lists (by id or name), or make a new list with them when no list matches. Use when the user asks to save targets from rank_territory, new_surgeons or warm_paths. The plan limits how many lists; up to 500 surgeons each.

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": {
      "npis": "<npis>"
    },
    "name": "save_to_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
listNoAn existing list's id or name to add to.
nameNoName for a new list, or an existing list's name to add to it.
npisYes10-digit NPIs to add.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations declare a non-read-only, non-destructive, non-idempotent write; the description adds real context beyond that: a plan-imposed cap on number of lists, a 500-surgeon ceiling per list, and the implicit side effect of creating a list. It is silent on duplicate handling and on what happens when the plan limit is already reached.

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 tight sentences, front-loaded with the action and the create-if-missing branch, followed by the trigger context and the limits. No filler.

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 write tool with no output schema, the definition covers the action, the trigger, the create branch, and quota constraints, which is close to sufficient. Missing is any statement of what is returned (e.g., list id) or how partial failures and duplicates are handled.

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 description largely restates what the schema already says about list (id or name), name (new or existing), and the 500-NPI cap. It adds no disambiguation for what happens if both list and name are supplied, so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource: add surgeons by NPI to a rep's prospect list, with an explicit upsert branch (create a new list when no list matches). That is enough to separate it from my_lists (which lists lists) and update_list_item (which edits existing entries).

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives concrete when-to-use guidance by naming the three upstream tools whose output it consumes (rank_territory, new_surgeons, warm_paths). It does not state when NOT to use it or point at alternatives for adding a single surgeon or renaming a list, so it stops short of full routing.

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