Skip to main content
Glama

MedaRep

Set where an account stands

set_account_status
DestructiveIdempotent

Set where a surgeon stands in a product segment: target, contacted, trialing, using_us, competitor (with which competitor, if known), lost, passed or unknown. A surgeon can be a customer in one segment and a target in another (using us for sports medicine, not yet for shoulder), so name the segment when the rep does; omit it for the surgeon in general. With using_us, share says how much of their cases in the segment the rep has (some, half, most, all): a customer at some or half is room to grow. using_us also marks them a customer (warm paths start from them); lost from using_us unmarks them unless another segment is still using us. Every change is kept in the history. Shared with the rep's team.

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": {
      "npi": "<npi>",
      "status": "<status>"
    },
    "name": "set_account_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
npiYes10-digit NPI; use search to find it.
shareNoWith using_us: how much of their cases in the segment the rep has.
statusYes
segmentNoThe product segment: ortho, spine-pain, biologics, cardio, neuro, gensurg, uro-gyn, ent, eye, onc-ir or dme (a procedure key such as knee-arthroplasty reads as its segment). Omit for the surgeon in general.
competitorNoWith competitor or lost: the company they use as the company reports it, e.g. Stryker.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already flag a destructive, non-read-only, idempotent, closed-world write, and the description adds genuinely non-obvious side effects: every change is recorded in history, changes are visible to the rep's team, using_us implicitly marks the surgeon a customer, and lost unmarks them unless another segment is still using_us. It still doesn't say what existing data a status change destroys or whether a lost status can be reverted, which is the main gap for a destructive operation.

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?

One dense, front-loaded paragraph that leads with the status set and then layers the segment, share, customer-marking and history rules; nearly every clause encodes a business rule rather than restating the schema, and parenthetical examples carry their weight.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a five-parameter mutation with no output schema, the definition covers status semantics, cross-segment independence, conditional parameter use and downstream side effects (history, team visibility, customer marking) — everything an agent needs to call it correctly and understand the consequences.

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 80%, so the schema already defines most parameters; the description still adds interpretation the schema lacks — that share is only meaningful with using_us and that some/half signals room to grow, and that segment should be omitted for the surgeon generally rather than defaulted. The competitor guidance is lighter than the schema's ('with competitor or lost'), which is the only shortfall.

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 states a specific verb ('Set') and resource ('where a surgeon stands in a product segment') and then enumerates the full status vocabulary, so an agent knows exactly what this tool writes and to what value space.

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 real conditional guidance: name the segment when the rep names one, omit it for the surgeon in general, and pair 'share' only with using_us. What's missing is any routing versus siblings such as set_follow_up or add_note, so the when-not-to-use-this-tool case is left implicit.

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