Skip to main content
Glama

MedaRep

Set a line I carry

set_my_lines
DestructiveIdempotent

Add a company the rep sells, optionally narrowed to some of its brands (e.g. company "Stryker", brands ["Triathlon", "Mako"]); saving a company again replaces its brands, and none means the whole company. With remove true, drop that company. Use only when the user says what they sell.

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": {
      "company": "<company>"
    },
    "name": "set_my_lines"
  }
}

Input Schema

NameRequiredDescriptionDefault
brandsNoBrand names the rep carries; omit for the whole company.
removeNotrue to remove this company from the rep's lines.
companyYesThe company as it reports to Open Payments, e.g. Stryker, Zimmer Biomet, Johnson & Johnson MedTech.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already flag destructiveHint=true and idempotentHint=true; the description goes further by explaining the exact destruction model ('saving a company again replaces its brands') and the default scope ('none means the whole company'). It stops short of saying what confirmation is expected or what the response looks like, but the replace-vs-append semantics are the key risk and are covered.

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?

The core action and its brand example come first, with the remove path and the usage gate trailing in a single dense paragraph. It is slightly run-on across semicolons, but no sentence 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?

For a 3-parameter mutation tool with no output schema, the definition covers add, replace, whole-company default, and delete, plus a usage gate. Missing only return behavior and error/prerequisite conditions, which are modest gaps given full annotation and schema coverage.

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 baseline is 3, but the description adds real meaning beyond the schema: 'brands' is a replacement set rather than a union, omitting it means the entire company, and remove=true is a delete path rather than a toggle off. The schema alone would leave the replace-vs-append ambiguity unresolved.

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 ('Add a company the rep sells') and enumerates the three behaviors the tool actually has: add-narrowed-to-brands, replace-brands-on-resave, and remove-by-flag. An agent can distinguish this from the read-side sibling 'my_lines' purely from the text.

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?

'Use only when the user says what they sell' gives a clear positive condition and implicitly excludes the case where the user is merely asking what they carry. It does not name the read alternative (my_lines) explicitly, so the routing is clear but not fully closed.

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