SiteCheck Shop & Social

SingleCare prescription coupon prices for a drug: price

ecommerce_singlecare

Read-only

SingleCare prescription coupon prices for a drug: price at each nearby pharmacy (Kroger, CVS, Walgreens, Walmart...) with loyalty price and distance, the lowest price, form, strength and quantity priced, usual retail cash price, generic/brand flag and monthly price history. From singlecare.com's public drug pages via a residential proxy; the pharmacy list depends on the ZIP. Related tools on this server, for a different need: ecommerce_costplusdrugs when you need Cost Plus Drugs mail-order cash prices from its official; ecommerce_newegg when you need Newegg product search: item number, title, model, price. Price: $0.002 in USDC per successful call, paid with x402 (Base, Solana or Arc); failed calls are not charged.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "drug": "<drug>"
    },
    "name": "ecommerce_singlecare"
  }
}

Input Schema

Name	Required	Description	Default
`zip`	No	Optional 5-digit US ZIP code for nearby pharmacies
`drug`	Yes	Drug name as in singlecare.com/prescription/<name>, e.g. lipitor, atorvastatin-calcium, amoxicillin

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 23, 2026

TDQS

A4.5/5.0

Behavior5/5

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

Goes well beyond readOnlyHint/openWorldHint by disclosing the data source (singlecare.com public drug pages), that access goes through a residential proxy, that the pharmacy list varies by ZIP, and the exact billing model — $0.002 USDC per successful call via x402 on Base/Solana/Arc with failed calls not charged. That cost and coverage information is operationally decisive and unavailable from annotations.

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

Conciseness3/5

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

Front-loaded correctly with purpose first and the cost model last, but the long enumeration of returned fields (loyalty price, distance, lowest price, form, strength, quantity, retail cash price, generic/brand flag, monthly history) is redundant given an output schema exists. The core sentence is also a run-on that crowds the genuinely valuable proxy/ZIP/cost details.

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?

An output schema is present, so return values need no prose, and the description supplies the pieces an agent actually needs: source site, proxy behavior, ZIP-dependence, sibling alternatives, and a precise per-call price with failure terms. Nothing essential is missing for a two-parameter read-only lookup.

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 100% schema coverage the baseline is 3, but the description adds meaning the schema lacks: it explains that the returned pharmacy list depends on the ZIP, which the zip property description does not state ('Optional 5-digit US ZIP code for nearby pharmacies'). The drug parameter adds nothing beyond the schema, which already gives slug examples.

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?

Names a specific verb and resource: retrieve SingleCare coupon prices for a given drug at each nearby pharmacy, including lowest price and per-pharmacy detail. It also distinguishes itself from named siblings (costplusdrugs for mail-order cash prices, newegg for product search), so an agent can identify it without opening schemas.

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?

Explicitly routes the agent to alternatives: 'ecommerce_costplusdrugs when you need Cost Plus Drugs mail-order cash prices' and 'ecommerce_newegg when you need Newegg product search', framing them as 'for a different need'. It states the selection context clearly but offers no explicit exclusion or prerequisite guidance (e.g., when SingleCare coverage may be absent for a drug).

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

All SiteCheck Shop & Social 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?