Skip to main content
Glama

MedaRep

What changed since the last visit

changes_since
Read-onlyIdempotent

What changed for one surgeon since the rep last touched them (their last logged visit, status change or note; or since a given day, default 90 days): moves and practice changes, partners who joined or left, a new Open Payments year and any change of main company, a new Medicare year with the case change, and new FDA clearances and recalls from the companies engaged with them. With the rep's own record: status per line, recent visits, open follow-ups and notes. The first half of a pre-call brief; counts as opening the profile.

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

Input Schema

NameRequiredDescriptionDefault
npiYes10-digit NPI; use search to find it.
sinceNoYYYY-MM-DD; default the rep's last touch, or 90 days ago.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, and the description adds beyond that by disclosing that calling it 'counts as opening the profile' — a side effect an agent would otherwise not know. It also spells out which data sections come back. Pagination, size limits, and behavior for a surgeon with no history remain undisclosed.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The scope is front-loaded correctly in the first clause, but the middle sentence is a long colon-delimited run-on with dense business jargon that is hard to parse in one pass. Every element is informative, yet a bulleted or shorter phrasing would earn its place better.

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 only two parameters, no output schema, and annotations covering the safety profile, the description does most of the remaining work by listing return content and the default time window. It is nearly complete for a read-only digest, missing only result volume or truncation behavior.

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 100%, so the baseline would be 3, but the description adds real meaning by defining what 'last touch' means (last logged visit, status change, or note) and restating the 90-day fallback, which clarifies the semantics behind the 'since' parameter beyond the bare YYYY-MM-DD note.

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 verb-and-resource pairing ('what changed for one surgeon since the rep last touched them') and enumerates the content categories (practice moves, partner changes, Open Payments/Medicare year changes, FDA clearances and recalls) plus the rep-own-record section. An agent can tell this is a change digest rather than a full profile. It stops short of naming overlapping siblings such as new_clearances or ownership_changes, so sibling differentiation is only implied through 'The first half of a pre-call brief'.

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?

Usage context is stated clearly via 'The first half of a pre-call brief' and 'counts as opening the profile', which tells the agent when this tool is the right entry point. There are no explicit exclusions or 'use X instead when...' routing, so a 5 is not earned.

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