Skip to main content
Glama

MedaRep

Cross-sell to customers

cross_sell
Read-onlyIdempotent

More business in the accounts the rep already has: for each of their customers (marked on MedaRep), the procedures they do that one of the rep's lines covers (my_lines) where that line's company is not already the one most engaged with them for those products, with their Medicare cases, who engages them for those products now and how deeply, and why it ranks. Give one customer's NPI for theirs, or none for the best across all customers. Needs saved lines and marked customers.

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": "cross_sell"
  }
}

Input Schema

NameRequiredDescriptionDefault
npiNoOne customer's 10-digit NPI. Omit for the best across all customers.
limitNoHow many rows to return (default 25).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds value beyond that by disclosing the prerequisite state (saved lines and marked customers must exist or the tool yields nothing) and by describing what the rows contain, including competitive engagement depth and ranking rationale.

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

Conciseness2/5

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

The entire definition is one long run-on sentence with nested clauses and no front-loaded summary, making it slow to parse and hard to scan. Content is not padded so much as badly structured; a one-line purpose statement followed by prerequisites would serve far better.

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

Completeness3/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 main remaining burden is telling the agent what comes back and when results are empty. Prerequisites are covered and the row content is sketched, but the output shape ("why it ranks", engagement depth) stays abstract and no empty-result behavior is stated.

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 coverage is 100%, so both parameters are already documented, including the omit-for-all behavior of npi and the 1–100 range on limit. The description restates the npi semantics and implies rows are ranked, but adds no syntax, format, or edge-case detail the schema does not already carry.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description does convey a specific resource — cross-sell targets among a rep's marked customers, filtered to procedures covered by my_lines where the line's company is not the incumbent — but it is delivered as a single run-on clause chain with no leading verb or summary. An agent must parse the whole sentence to extract the purpose, and no sibling (e.g. opportunities, incumbents, coverage) is named for contrast.

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?

"Give one customer's NPI for theirs, or none for the best across all customers" gives explicit when-to-use guidance tied to the npi parameter, and "Needs saved lines and marked customers" states a hard prerequisite. It stops short of naming alternative tools for adjacent questions, so it is clear context without exclusions.

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