Skip to main content
Glama

loe-exposure

Server Details

Drug patent expiries ranked by the Medicare Part D spending exposed to them

If you are the author of this connector, you can claim ownership with GitHub, an HTTP challenge, or a DNS record. Claimed connector authors can inspect health checks, view analytics, and manage their listing.
Status
Healthy
Last Tested
Transport
Streamable HTTP · MCP 2024-11-05
URL

TDQS

Score is being calculated.

Available Tools

1 tool
loss_of_exclusivity_exposureAInspect

Rank upcoming FDA Orange Book patent and exclusivity expiries BY the gross Medicare Part D spending exposed to them, with marketed-generic status for each ranked drug resolved from live CMS NADAC price evidence. Answers which expiries matter, not merely which come first. Reports EXPOSURE, never forecast savings. Spending is gross of manufacturer rebates. Orange Book small molecules only, so biologics — among the largest Part D line items — are excluded, and the headline total must not be read as spending that will "go generic".

ParametersJSON Schema
NameRequiredDescriptionDefault
limitNoHow many drugs to rank, default 25
windowNoMonths ahead to include, default 24

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure, and it does a strong job: it clarifies that spending is gross of manufacturer rebates, that this is not a savings forecast, that only Orange Book small molecules are included, and that biologics are excluded. It does not mention output format, pagination, or potential failure modes, which prevents a 5.

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

Conciseness5/5

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

The description is front-loaded with the core purpose and ranking criterion, and each subsequent sentence adds a distinct caveat or clarification. There is no redundant or filler text, and the structure moves logically from what it does, to its ranking philosophy, to its important limitations.

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 tool with two optional parameters, no output schema, and no sibling tools, the description provides robust context: the ranking basis, the data source for generic status, the spending measure, and the exclusions. It does not state how results will be returned or how the limit/window parameters affect the output, but overall it is sufficiently complete for an agent to understand the tool's scope and intent.

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?

The input schema already documents both parameters with 100% coverage, including defaults ('default 25', 'default 24'), so the baseline is 3. The description does not add any extra semantics about how limit or window behave, but this is not a significant gap given the schema is complete.

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 states a specific verb ('Rank') applied to a specific resource (upcoming FDA Orange Book patent and exclusivity expiries) with a clear ranking criterion (gross Medicare Part D spending exposure). It also distinguishes itself from a mere chronological expiry list by saying it 'answers which expiries matter, not merely which come first.'

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?

The description gives clear context for when to use the tool: when prioritization by Part D spending exposure is needed rather than chronological ordering. It also provides explicit exclusions and caveats, such as small molecules only, biologics excluded, and that it reports exposure rather than savings forecasts. There are no named alternatives, but the negative guidance effectively clarifies what this tool is not for.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

  1. 1 tool update
    • First observedloss_of_exclusivity_exposure

Related MCP Connectors

Related MCP Servers

  • A
    license
    Not graded
    quality
    C
    maintenance
    Queries US prescription drug use by medical condition from AHRQ's Medical Expenditure Panel Survey — which drugs Americans take for a given condition, what a drug is prescribed for, and national volume, spending and out-of-pocket share for individual drugs or the top drugs of a year. Every response carries sample sizes and reliability flags so estimates are treated as rough magnitude and ranking rather than precise counts.
    0
    MIT
  • F
    license
    Not graded
    quality
    C
    maintenance
    Provides unified access to drug formulary data from US ACA marketplace health insurance plans, enabling drug search, coverage details, restriction info, and plan comparison across thousands of plans.
    -
Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources