Skip to main content
Glama

RateCard Health

2026 Healthcare B2B Advertising Price Index

get_price_index
Read-onlyIdempotent

Aggregate ad-price benchmarks (CC BY 4.0) across healthcare B2B rate cards: median/quartile entry prices and derived CPMs (rounded, or banded; medians only for groups with 5+ rate cards), by format, category and price band. Optionally filter by group_type (all, format, category, entry_price_band) or group name.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

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

Input Schema

NameRequiredDescriptionDefault
groupNoe.g. "Nursing", "E-newsletter", "Print"
group_typeNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior4/5

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

Adds substantial detail that the readOnly/idempotent/openWorld=false annotations do not: a minimum sample threshold ('medians only for groups with 5+ rate cards'), value rounding/banding behavior, and CC BY 4.0 licensing. These are exactly the caveats an agent needs to interpret sparse or suppressed results. Minor gap: no statement that results are a static published index rather than live data.

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?

Two sentences, no filler, with the most decision-relevant facts (what's aggregated, granularity, filtering) up front. The parenthetical about rounding and the 5+ threshold is dense but earns its place. Slight crowding of caveats into one long sentence costs it a point.

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 carries the burden of describing returns and does so: medians/quartiles/CPMs, rounded or banded, minimum group size. What's missing is unit/currency and the shape of the response (flat rows vs. grouped), which matters for a filterable aggregate query.

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 50% — 'group' has only an example string and 'group_type' has only an enum with no prose. The description partially compensates by enumerating the four group_type values and framing 'group' as a group-name filter, but it never says how 'group' relates to 'group_type' (e.g. does a bare group name imply a type?). The schema does most of the work here, so baseline 3.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

Opens with a specific verb+resource ('Aggregate ad-price benchmarks'), then narrows to concrete outputs (median/quartile entry prices, derived CPMs) scoped to healthcare B2B rate cards. An agent can immediately tell this is an aggregate-stats tool, not a listing tool. It never names a sibling to contrast with, though the noun phrase differs enough from get_publication/search_publications to be workable.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The only guidance is 'Optionally filter by group_type ... or group name,' which is parameter mechanics rather than tool-selection advice. Nothing says when to use this versus get_free_sample or search_publications, nor whether it is safe to call with no arguments (all params are optional, yet the description doesn't confirm the default scope).

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