Skip to main content
Glama

MedaRep

My customers

my_customers
DestructiveIdempotent

The surgeons the rep already sells to, which warm_paths starts from. Give an npi to mark that surgeon a customer, or an npi with customer false to unmark them; omit both to list them.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "my_customers"
  }
}

Input Schema

NameRequiredDescriptionDefault
npiNo10-digit NPI; use search to find it.
customerNoWith npi: true to mark (the default), false to unmark.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

The annotations already declare destructive (destructiveHint=true) and idempotent behavior. The description adds that unmarking a surgeon silently changes their customer status, which the annotations alone do not convey. It does not say what happens if an unknown NPI is passed, or whether unmarking removes any visit history.

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?

A single dense sentence puts the resource first, the runtime modes second, and the list behavior last. Nothing is repeated or wasted.

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 two-parameter tool with no output schema and full annotation coverage, the description says enough to call the tool correctly in all three modes. Only edge-case behavior (invalid NPI, what unmarking destroys) is left unstated, which is a minor gap given the destructive annotation.

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?

The input schema documents both parameters at 100% coverage, including the default true for customer. The description adds one thing the schema does not: the effect of omitting both parameters is to list customers. That is a marginal gain over a schema that already does the heavy lifting.

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 concrete resource ('the surgeons the rep already sells to') and describes two distinct modes: listing customers and mutating a surgeon's customer flag. It also foregrounds the relation to the warm_paths sibling ('which warm_paths starts from'). The purpose is clear, although the verb and resource are not stated as cleanly as a single-action tool would be.

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?

The description gives an explicit invocation rule for each mode: pass npi to mark, pass npi plus customer=false to unmark, and omit both to list. It also names warm_paths as the downstream consumer, which helps the agent decide when to use this tool first. It does not state when not to use this tool, or a prerequisite such as needing an existing NPI.

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