Skip to main content
Glama

find_us_equivalent

Read-onlyIdempotent

Find out what a medicine from another country is in the US, and what it costs.

Use when the person names a medicine that is not a US product — a brand from
home (No-Spa, Nurofen, Dolo-Neurobion, 999 Ganmaoling), a name in another
script (Но-шпа, 泰诺), or an ingredient the US calls something else
(paracetamol) — or asks "what is this called in the US?". Optional ``country``
picks between brands of the same name sold in different places; ``locale`` is
a language code (leave it out and the host's own locale is used).

Returns the reviewed entry: ``usClass`` (``same_inn`` = the same active
ingredient is sold here, ``rx_alternative`` = it is not and the closest US
options need a prescription, ``no_equivalent`` = nothing here matches),
``guidance`` (ONE vetted sentence, written to be quoted word for word),
``inn``, ``usGeneric``, ``usBrands``, ``rxStatus``, ``notes``, ``components``,
``usDrug`` (slug, lowest observed price and the date it was observed),
``savingsCard`` when there is a US drug to fill, ``pageUrl``, and
``otherMatches`` when the same brand name exists in more than one country.
``found`` is false when nothing matched.

Next: quote ``guidance`` as written, then say ``guidanceDisclaimer``. With a
``usDrug``, call compare_prices (or get_drug) for its slug, give the price
WITH its observation date, and offer the free card.

Do not call the US drug the same product, do not suggest swapping one for the
other, and for ``rx_alternative`` or ``no_equivalent`` do not name a
substitute at all — send the person to a pharmacist or a doctor. Do not
translate or reword ``guidance``; it is reviewed text.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
brandYes
localeNo
channelNomcp
countryNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.9/5.0
Behavior5/5

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

Beyond the read-only/idempotent annotations, the description discloses reviewed-text status, exact usClass meanings, disambiguation behavior for country/locale, otherMatches behavior, savingsCard availability, and found=false edge case, with no contradiction to annotations.

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 dense but front-loaded with purpose, then flows from trigger conditions to parameters, return semantics, required follow-up, and safety constraints. No sentence is filler; length is justified by the tool's medical-safety complexity.

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?

The description covers trigger cases, parameter behavior, output classes, quoted guidance handling, downstream tool calls, and what not to say, which is complete for a high-stakes lookup tool. The presence of an output schema also covers raw return shape.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With schema coverage at 0%, the description compensates by explaining country (brand disambiguation), locale (language code plus host-locale fallback), and brand (through examples and the medicine-name context). Only the internal 'channel' parameter is left undocumented, which is minor due to its default.

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 opens with a specific verb-resource pair ('Find out what a medicine from another country is in the US, and what it costs') and gives concrete trigger examples, which makes the tool's scope unmistakable and distinguishes it from reverse-lookup siblings.

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

Usage Guidelines5/5

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

It explicitly states when to use the tool ('Use when the person names a medicine that is not a US product... or asks what is this called in the US?') and provides follow-up tool routing ('call compare_prices (or get_drug)'), along with explicit do-nots for unsafe substitutions.

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