Skip to main content
Glama

GLPcompare: US GLP-1 cash prices

Find a seller's GLP-1 prices

find_seller_glp1_prices
Read-onlyIdempotent

Current US self-pay GLP-1 prices of one seller, such as Ro, Hims & Hers, LillyDirect or Wellmedr, ranked by cost per 30 days. Only prices that state the supply they buy are ranked; its other current prices follow in other_prices, each with why it is not ranked. Returns each product, cost per 30 days, the seller's own price wording, the check date, the source page and the seller's page on GLPcompare.

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": {
      "seller": "<seller>"
    },
    "name": "find_seller_glp1_prices"
  }
}

Input Schema

NameRequiredDescriptionDefault
sellerYesThe seller's name, e.g. "Ro" or "Hims".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior5/5

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

Annotations already cover read-only, idempotent, non-destructive and closed-world, yet the description still adds substantial behavior: only prices disclosing supply are ranked, non-conforming prices are demoted to other_prices with a stated reason, and the exact return payload is enumerated. That is real context beyond the structured fields.

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?

Three sentences, front-loaded with the core purpose, then ranking rule, then return shape. With no output schema the return enumeration earns its place, though the sentence runs long and the 'such as' seller list is somewhat decorative.

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?

For a single-parameter, read-only lookup with no output schema, the description covers purpose, ranking policy, fallback bucket and returned fields — enough to call it confidently. The remaining gap is behavior for an unrecognized or missing seller name, which an agent would want to know before invoking.

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 100% and the single 'seller' parameter is already documented with examples, so the baseline is 3. The description's seller list (Ro, Hims & Hers, LillyDirect, Wellmedr) hints at the expected naming convention but largely restates the schema's example rather than adding new semantics such as matching behavior for unknown names.

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 first sentence states a specific verb and resource ('Current US self-pay GLP-1 prices of one seller'), and the 'one seller' scoping meaningfully separates it from the catalog-level find_glp1_prices. It stops short of naming that sibling, so an agent must infer the routing rather than read it.

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

Usage Guidelines3/5

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

Usage is only implied: the 'of one seller' phrasing suggests this is the tool to reach for when a seller is known, but there is no explicit when-to-use or when-not statement and no named alternative. Nothing is misleading, but the agent gets no routing rule.

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