Skip to main content
Glama
Sign In

GLP Chart

by com.glpchart
OverviewDiscussionsAdmin

List GLP-1 programs and prices

get_programs
Read-only

Every US GLP-1 telehealth program GLP Chart rates, cheapest first, with its verified total monthly cost, its score and its lock-in terms. Filter by drug, US state or price ceiling.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_programs"
  }
}

Input Schema

NameRequiredDescriptionDefault
drugNoRestrict to programs that publish a price for one drug. One of: wegovy, zepbound, ozempic, mounjaro, rybelsus, sema_compounded, tirz_compounded, liraglutide. Plain names such as "compounded semaglutide" are accepted.
limitNoHow many rows to return. Default 10, maximum 50.
stateNoTwo-letter code or state name, e.g. "CA" or "California".
max_priceNoOnly programs at or below this monthly figure, in USD.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description goes beyond them by disclosing what the rows contain (verified total monthly cost, score, lock-in terms) and the default sort order, which is genuinely useful since there is no output schema to convey return shape.

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

Conciseness5/5

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

Two sentences, no filler, with the core scope and sort order front-loaded before the filtering clause. Every sentence 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 four-parameter list tool with no output schema, the description covers scope, ordering, row contents and filter options — enough to call it correctly. The only minor gap is pagination/limit behavior, which the schema already handles.

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 100%, so all four parameters (drug, limit, state, max_price) are already fully documented, including accepted plain names for drug. The description only restates the filter dimensions and adds no syntax or edge-case meaning beyond the schema, which is the baseline for full coverage.

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 names a specific verb and resource ('Every US GLP-1 telehealth program GLP Chart rates') plus the ordering rule ('cheapest first'), so an agent can immediately tell this is a list/ranking tool. It is distinguishable from siblings like get_price (single price lookup) and cheapest without opening any schema.

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 'Filter by drug, US state or price ceiling,' which tells the agent the three narrowing dimensions. However, it never states when to prefer this over the sibling tools (get_price, cheapest, fair_price) or when it would be the wrong choice, leaving routing to inference.

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

All GLP Chart 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