FineRx

open_price_finder

Read-onlyIdempotent

Open the FineRx search inside the card, so the person can look a medicine up themselves.

Use when the person asks to open FineRx, wants to search or browse on their
own, or is not sure of the name. Optional ``query`` pre-fills the search
(a medicine, a brand from another country, a misspelling). The card then
suggests matches as they type, each with where its card prices start and
the date, and a pick shows card prices by chain near a place they choose.

Returns the matches for ``query`` (if any), foreign brands that matched,
a few often-searched medicines, and the card. What the person picks in the
card reaches you as context. Hosts without MCP Apps get the matches as text.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`query`	No
`locale`	No

Schema Changelog

Changes observed during successful MCP inspections.

AddedSep 23, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, covering the safety profile. The description adds useful behavioral context: the interactive nature (card suggestions as the user types), the return of matches and foreign brands, and how user picks become context. It also notes the text fallback for non-MCP hosts, which goes beyond annotations. No contradiction found.

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 a single, well-structured paragraph that opens with the core purpose, then usage, then detailed behavior and return values. It is slightly long but every sentence adds value. The information is logically ordered and front-loaded with the main purpose.

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

Completeness3/5

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

The description covers the return content (matches, foreign brands, often-searched medicines, the card), the interactive flow, and the text fallback. However, it omits explanation for the 'locale' parameter, which is a notable gap given there is no output schema and the schema itself provides no descriptions. The absence of locale guidance makes the tool incomplete for an agent.

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 explain both parameters. It thoroughly explains 'query' with examples (a medicine, a foreign brand, a misspelling) and its pre-fill effect. However, 'locale' is never mentioned in the description, leaving a required parameter unexplained. This partial coverage prevents a higher score.

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 clearly states the tool opens the FineRx search UI so the user can browse. It specifies the resource ('FineRx search inside the card') and distinguishes it from direct search tools by emphasizing the self-service browsing aspect. This clearly separates it from siblings like search_drugs or ui_suggest.

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 explicitly lists when to use: when the person asks to open FineRx, wants to search/browse on their own, or is unsure of the name. It also mentions the behavior for hosts without MCP Apps, hinting at a fallback. However, it does not explicitly name alternative tools or state when not to use it, which is a minor gap.

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

All FineRx tools Inspect

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

Need Help?