Skip to main content
Glama

Stratalize Intelligence

Get Cost Plus Price

get_cost_plus_price
Read-only

Use when a patient, benefits manager, or procurement agent needs Mark Cuban Cost Plus Drugs transparent retail pricing for a specific NDC. Returns medication_name, brand_name, form, unit_price and unit_billing_price labeled transparent retail price estimate (cost+15% model), optional quantity quote, and canonical purchase URL — never labeled as a benchmark. Example: NDC 42385096230 — unit price $0.963 transparent retail price estimate (cost+15% model). Source: Cost Plus Drugs public API. | x402 SLA: $0.02 USDC per call. Returns HTTP 503 (no charge) when upstream data sources unavailable. data_sources[] discloses estimate provenance bound by synthesis.output_hash.

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": {
      "ndc_or_name": "<ndc_or_name>"
    },
    "name": "get_cost_plus_price"
  }
}

Input Schema

NameRequiredDescriptionDefault
ndc_or_nameYes
quantity_unitsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is covered. The description still adds real value beyond them: the cost+15% pricing model, the $0.02 USDC per-call charge, the 503-with-no-charge failure mode, and the data_sources[]/output_hash provenance binding. However, the SLA and provenance tail reads as boilerplate appended after a pipe rather than tightly integrated behavioral guidance, and it does not describe latency, rate limits, or caching.

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?

Front-loaded with the usage trigger, which is good, but the label 'transparent retail price estimate (cost+15% model)' is repeated verbatim in the return list and again in the example, and the pipe-delimited SLA/provenance tail is dense boilerplate. Roughly a sentence or two of the text is redundant.

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 no output schema, enumerating the returned fields (medication_name, brand_name, form, unit_price, unit_billing_price, purchase URL) is genuinely necessary and done well, and the failure mode and per-call cost are disclosed. The main gap is input-side: the accepted forms of ndc_or_name and the behavior of quantity_units remain unexplained.

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 description coverage is 0%, so the description must carry parameter meaning. It clarifies that the identifier is an NDC and that a quantity quote is optional, which maps loosely to ndc_or_name and quantity_units, but it never explains that ndc_or_name also accepts a drug name despite the parameter name, and gives no units, defaults, or format rules for quantity_units.

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?

States a specific verb (retrieve transparent retail pricing) and resource (Mark Cuban Cost Plus Drugs pricing for a given NDC), with the intended audience named up front. It also explicitly separates itself from the benchmark-style siblings by stating the value is 'never labeled as a benchmark.'

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 when a patient, benefits manager, or procurement agent needs ...' gives a clear triggering context, and the 'never labeled as a benchmark' clause hints at which sibling tools cover benchmark pricing. It stops short of naming an explicit alternative tool or stating a when-not condition.

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