Skip to main content
Glama

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

A4.3/5.0
Behavior5/5

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

Goes well beyond annotations (readOnly, openWorld, non-destructive) by disclosing the metered cost ($0.02 USDC per call), the failure contract (HTTP 503 with no charge when upstream sources are unavailable), and provenance disclosure via data_sources[]. That is exactly the operational context an agent cannot get from structured fields.

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 with the usage trigger and core return payload, then cost/error terms. The example and the closing 'data_sources[] ... bound by synthesis.output_hash' line are dense jargon that adds little for tool selection, but the overall length is justified by the information density.

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, the description does the work of enumerating return fields, the pricing model (cost+15%), the quote behavior, the URL, the fee, and the failure mode. Remaining gaps are the name-input path for ndc_or_name and the exact semantics of quantity_units, so it is strong but not airtight.

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 0%, so the description must carry both parameters. It does clarify that a quantity quote is optional (mapping to quantity_units) and gives a concrete NDC example, but it never explains that ndc_or_name also accepts a drug name or what format that takes — a meaningful gap at 0% coverage.

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 and resource: transparent retail pricing for a specific NDC, with named output fields (medication_name, brand_name, form, unit_price). The clause 'never labeled as a benchmark' actively separates it from the many benchmark siblings in the catalog, so an agent can route correctly without opening a schema.

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 caller-oriented trigger condition. It also implicitly excludes the benchmark-class tools, but no sibling is named as an explicit alternative, so it stops short of full when/when-not guidance.

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