Skip to main content
Glama

MedaRep

Update a surgeon on a list

update_list_item
DestructiveIdempotent

Set where a listed surgeon stands (target, contacted, trialing, using_us, competitor, lost, passed) or add a note to their thread, e.g. after a call. The stage is the account's own, for the surgeon in general: it reads the same on every list and the profile, and set_account_status sets it for one product segment. using_us (or its old name, customer) also marks them as the rep's customer for warm_paths; moving off it unmarks them.

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": {
      "list": "<list>",
      "npi": "<npi>"
    },
    "name": "update_list_item"
  }
}

Input Schema

NameRequiredDescriptionDefault
npiYes10-digit NPI; use search to find it.
listYesThe list's id or name.
noteNoAdds a note to the surgeon's thread on this list; earlier notes stay.
statusNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Beyond the annotations (destructiveHint=true, idempotentHint=true, openWorldHint=false), the description discloses real side effects: the stage is account-level and reads identically on every list and the profile, and using_us (alias customer) marks the surgeon as the rep's customer for warm_paths while moving off it unmarks them. That explains much of the destructive framing. It still doesn't say what permissions are needed or what happens on an invalid list/status.

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?

Three sentences, front-loaded with the primary action and status vocabulary before the scoping caveat and side-effect detail. It is dense with parentheticals ("or its old name, customer") but every clause carries information an agent needs; 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 mutation tool with no output schema, the description covers the two modes of operation, the shared-state semantics of status, the alias, and the warm_paths side effect — enough to call it correctly. Missing only error/permission behavior and confirmation of whether a status change disturbs existing notes, which is partially implied by "earlier notes stay."

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?

Schema coverage is 75%, and the biggest gap — the status enum having no per-value description in the schema — is filled by the description, which lists all values and explains that customer is a legacy alias for using_us and what that value does downstream. Note, list and npi are already documented in the schema, so the description's marginal gain is concentrated where it matters.

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?

The description opens with a specific verb and resource ("Set where a listed surgeon stands") and enumerates the full status vocabulary, so the agent knows exactly what can be changed. It also distinguishes the tool from set_account_status by scope (account-wide vs. one product segment), which no other field provides.

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?

It gives clear usage context ("e.g. after a call") and an explicit contrast with set_account_status for the account-level vs. segment-level distinction. It does not address when to use this versus the add_note sibling, even though adding a note is one of this tool's two modes — that overlap is left to inference.

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