Skip to main content
Glama

MedaRep

Add a note on a surgeon

add_note

Keep a note on a surgeon's account record that is not a visit: who decides, what they prefer, when to catch them, what a staff member said. Shared with the rep's team like visits, sent to a connected HubSpot as a note on the contact, and read back with the record (changes_since). For something that happened with the surgeon on a day, use log_visit and its note. Notes that read like patient information are refused.

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

Input Schema

NameRequiredDescriptionDefault
npiYes10-digit NPI; use search to find it.
noteYesThe note, without any patient information.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Goes well past the annotations by disclosing side effects the schema does not: the note is team-shared like visits, mirrored to a connected HubSpot as a contact note, and read back via changes_since. It also discloses a validation refusal rule. It stops short of covering duplicate creation on retry (idempotentHint is false) or any required permissions.

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?

Front-loaded and dense with no filler, but the middle sentence strings four clauses together (sharing, HubSpot sync, changes_since readback) and reads as a run-on. Slight restructuring would preserve all the content with less parsing effort.

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 two-parameter write tool with no output schema, the definition covers purpose, exclusion, routing alternative, visibility, downstream sync, readback path, and rejection behavior. Nothing an agent needs in order to call this correctly is missing.

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 is 3, but the description earns more by explaining what content belongs in `note` (who decides, preferences, timing, hearsay) and reinforcing the no-patient-information constraint on that field. The `npi` parameter is left to the schema, which already says to use search.

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?

Names a specific verb and resource ('keep a note on a surgeon's account record') and immediately draws the boundary that matters: 'that is not a visit.' The contrast with log_visit lets an agent distinguish the two without opening either schema.

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

Usage Guidelines5/5

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

Gives explicit routing rules in both directions: use this for durable facts (decision-maker, preferences, timing, staff remarks), and 'For something that happened with the surgeon on a day, use log_visit and its note.' It also states a hard refusal condition, so the agent knows when not to call at all.

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