Skip to main content
Glama

Mn Rx Price Growth

mn_rx_price_growth
Read-onlyIdempotent

Minnesota manufacturer disclosures of a prescription drug's Wholesale Acquisition Cost (WAC, published list price) increasing, filed under Minnesota's Prescription Drug Price Transparency program (Minn. Stat. 62J.84) with the Department of Health. Search by drug name/fragment, manufacturer, or NDC. Returns the WAC after the increase, the percent increase over the previous WAC, and the manufacturer's stated price-increase factors when disclosed. This is a periodic snapshot (not a live feed), the response carries data_as_of. California has a richer, live-queried equivalent, see ca-drug-price-transparency. Keyless.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

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

Input Schema

NameRequiredDescriptionDefault
ndcNoNational Drug Code, any common format.
drugNoDrug name or fragment, matched against the drug description.
limitNoMax records to return, 1-100 (default 25).
manufacturerNoManufacturer name or fragment.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld, non-destructive, so the safety profile is covered. The description adds genuinely new behavior: it is a periodic snapshot rather than a live feed, the response carries a `data_as_of` staleness marker, and access is keyless. It does not mention pagination or rate limits, but the staleness disclosure is the operationally important one.

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-loads the jurisdiction, data source, and program in the first sentence, then layers search keys, return fields, freshness, and the alternative. Dense but each clause carries information; only the full statutory citation is arguably surplus.

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

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema, so the description must carry return-value information — and it does, naming the post-increase WAC, percent increase, manufacturer factors, and the `data_as_of` marker. Freshness, authentication, and the cross-jurisdiction alternative are all covered, which is everything an agent needs before calling a four-parameter read tool.

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 100%, so every parameter is already documented with its matching semantics. The description's 'search by drug name/fragment, manufacturer, or NDC' merely restates the schema's fields in aggregate, adding no new format or precedence rules. Baseline 3 applies when the schema does the heavy lifting.

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: Minnesota manufacturer disclosures of WAC increases, with the statutory program named. It also scopes the exact data returned (post-increase WAC, percent increase, stated factors) and contrasts itself with the California equivalent, so it is distinguishable from siblings like mn_rx_new_drug_launches 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?

Gives concrete query paths (drug name/fragment, manufacturer, NDC) and explicitly routes agents wanting live, richer data to ca-drug-price-transparency. It stops short of stating when to prefer mn_rx_new_drug_launches over this tool, so the sibling differentiation is only partial.

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.