Skip to main content
Glama

Find GLP-1 Prices

find_glp1_prices
Read-only

Current US self-pay prices of a compounded GLP-1 medication (semaglutide or tirzepatide, injectable) from GLP-1 Buyer Guide's dated records, returned in the guide's ranked order (score-based), standard month-to-month plans only. Each result names its source page and check date.

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": {
      "medication": "<medication>"
    },
    "name": "find_glp1_prices"
  }
}

Input Schema

NameRequiredDescriptionDefault
medicationYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already cover read-only, closed-world, non-destructive, so the description adds value by disclosing data provenance (dated guide records), freshness signals (check date per result), ordering semantics (score-based ranked order), and an explicit exclusion of non-standard plans. It doesn't mention coverage limits, rate limits, or what happens when no records match, which keeps it below 5.

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?

One front-loaded sentence carrying purpose, scope, source, ordering, and return content with no filler. The stacked parenthetical qualifiers are dense but each earns its place.

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 read-only, single-parameter lookup with no output schema, the description covers source, ordering, filtering, and the shape of each result (source page and check date). Missing only edge-case behavior such as empty results or price field contents.

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?

The single parameter is an enum with the two values already enumerated in the schema, so the description's main addition is framing both as compounded injectables in the US. Schema description coverage is 0%, but the enum itself makes the parameter self-explanatory; the description adds modest context rather than new detail.

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?

States a specific verb and resource (find prices) plus strong scope qualifiers: US, self-pay, compounded GLP-1 (semaglutide/tirzepatide injectable), sourced from GLP-1 Buyer Guide records. It does not explicitly name or contrast with find_provider_glp1_prices, so sibling differentiation is only implied by 'compounded' and 'self-pay'.

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 implied by the scoping terms (self-pay, compounded, standard month-to-month plans only), which tells the agent this is not for insurance-covered or promotional pricing. However, there is no explicit when-to-use/when-not statement or pointer to the sibling tool for provider prices.

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