Skip to main content
Glama

MedaRep

Log a visit

log_visit

Record a visit with a surgeon on the rep's account: a case covered, a meeting, a call, an in-service or a meal, on a date (default today), with an optional short note and the facility's CCN. Shared with the rep's team as customers are. Notes that read like patient information are refused with the reason; a meal comes back with a reminder about Open Payments reporting. Use when the rep tells you about a visit, after reading back what you will save.

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>",
      "kind": "<kind>"
    },
    "name": "log_visit"
  }
}

Input Schema

NameRequiredDescriptionDefault
onNoThe day, YYYY-MM-DD; default today. Not in the future.
npiYes10-digit NPI; use search to find it.
kindYes
noteNoWhat happened, without any patient information.
outcomeNoHow it went, when the rep says: a good conversation, they want a trial, not now, they are on a competitor, or no access. The answer says what to offer next.
facilityNoThe hospital or ASC's six-character CCN, when the visit was there (search finds it).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior5/5

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

Beyond the annotations (non-read-only, non-destructive, non-idempotent), the description discloses visibility ("Shared with the rep's team"), a validation rule with its failure mode (patient-like notes are refused with a reason), and a side effect on response content (a meal returns an Open Payments reminder). These are behavioral facts an agent could not infer from the structured fields.

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?

Purpose and enumerated kinds are front-loaded, and the closing sentence carries the trigger and precondition. The first sentence is long and clause-heavy, but no clause is 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?

With no output schema, the description does a lot: it covers visibility, validation refusal, and the meal-specific reminder. It leaves unstated what the tool returns (e.g., a visit identifier) and how duplicate visits are treated despite idempotentHint=false, which keeps it just short of complete.

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 83%, so the schema already documents date defaulting to today, the NPI lookup, the note length and the CCN. The description restates date default and the optional short note and CCN without adding syntax or constraints beyond the schema, so the baseline of 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?

The description names a specific verb and resource ("Record a visit with a surgeon") and enumerates the visit kinds (case, meeting, call, in-service, meal), so an agent knows exactly what this creates. It also scopes it to the rep's account, which separates it from generic note-writing siblings like add_note.

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 an explicit trigger ("Use when the rep tells you about a visit") plus a workflow precondition ("after reading back what you will save"). It does not name an alternative for related-but-different cases such as logging a freeform note, so it stops short of full when/when-not 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