Skip to main content
Glama

Find Provider GLP-1 Prices

find_provider_glp1_prices
Read-only

Every recorded GLP-1 price from one provider in GLP-1 Buyer Guide's records, with 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": {
      "provider": "<provider>"
    },
    "name": "find_provider_glp1_prices"
  }
}

Input Schema

NameRequiredDescriptionDefault
providerYes

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 the safety profile (readOnly, non-destructive, closed-world), so the bar is lower. The description still adds meaningful context beyond them: the data comes from a recorded price guide rather than live lookups, and each result carries a source page and check date, which signals provenance and staleness considerations.

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?

One tightly written sentence that front-loads the result scope and appends the provenance fields; there is no filler or redundancy.

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?

With no output schema, the description helpfully names the returned fields (source page, check date) and the data source. It still leaves the provider identifier format and empty-result behavior unspecified, which matters for a lookup tool keyed on a free-text parameter.

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 0% for the single 'provider' parameter, and the description only implies it is a provider identifier without specifying the expected form (name, ID, slug) or behavior on non-matching providers. It adds a little meaning but does not fully compensate for the undocumented schema.

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 description states a specific resource and scope: every recorded GLP-1 price from one provider, drawn from GLP-1 Buyer Guide records. The 'from one provider' framing distinguishes it from the broad sibling find_glp1_prices, though it never names that sibling explicitly.

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: an agent can infer this is the tool for a single provider's price history, but there is no statement of when to prefer it over find_glp1_prices or list_glp1_medications, and no exclusions or prerequisites are given.

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