Skip to main content
Glama

FineRx

by com.finerxfinder
OverviewDiscussionsAdmin

find_us_equivalent

Read-onlyIdempotent

What a medicine from another country is in the US, and its card price here.

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.

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, to be quoted word for word),
``guidanceDisclaimer``, ``inn``, ``usGeneric``, ``usBrands``, ``rxStatus``,
``usDrug`` (slug and the card price from which it was seen, with the date),
``otherMatches`` for the same brand name in other countries, and the card.
``found`` is false when nothing matched.

Next: quote ``guidance`` as written, then ``guidanceDisclaimer``. With a
``usDrug``, compare_prices for its slug. Do not call the US drug the same
product or suggest swapping; for ``rx_alternative`` and ``no_equivalent``
name no substitute — send the person to a pharmacist or a doctor.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
brandYes
localeNo
channelNo
countryNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • addedInput schema / properties / channel / anyOf
      Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]
    • changedInput schema / properties / channel / default
      Previous value: -"mcp"New value: +null
    • removedInput schema / properties / channel / type
      Removed value: -"string"
    • changedOutput schema / (root)
      Previous value: -{
-  "additionalProperties": true,
-  "title": "find_us_equivalentDictOutput",
-  "type": "object"
-}New value: +null
  2. Added

TDQS

A4.1/5.0
Behavior5/5

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

Beyond the readOnly/idempotent annotations, the description reveals essential behaviors: guidance must be quoted word for word, guidanceDisclaimer is returned, found is false when no match, and agents must never call the US drug the same product or suggest a substitute for rx_alternative/no_equivalent. This is substantial behavioral context annotations cannot convey.

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?

The description is longer than average, but each block earns its place: trigger conditions, return fields, and post-processing instructions. It is front-loaded with purpose and structured with plain-language punctuation, though the dense output-field paragraph could be slightly easier to scan.

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 explaining return values and does so thoroughly: usClass semantics, guidance usage, usDrug slug for compare_prices, otherMatches, and found. The only notable gap is the unexplained locale and channel parameters, which keeps this from a perfect score.

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 0%, so the description must supply parameter meaning. It adds strong meaning for brand (foreign medicine name with examples) and country (same brand sold in different places), but locale and channel are left entirely unexplained. Partial compensation across four parameters.

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?

The description opens with a clear statement of what the tool does ('What a medicine from another country is in the US, and its card price here') and gives extensive examples of non-US products and scripts. It makes the foreign-to-US mapping obvious, but it does not explicitly differentiate against sibling tools such as foreign_brands_for_drug, so it lacks the final comparative push for a 5.

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?

There is an explicit 'Use when...' section with concrete triggers (foreign brand, other script, paracetamol, 'what is this called in the US?'), and country is described for disambiguation. However, it does not name alternative tools or state when not to use it, so it stops short of explicit when-not/alternatives guidance.

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

All FineRx toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources