Skip to main content
Glama

List GLP-1 Medications

list_glp1_medications
Read-only

Medications GLP-1 Buyer Guide keeps a ranked injectable price list for, with counts.

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": "list_glp1_medications"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered by structured data. The description adds that the list is ranked and includes counts, but never says what the ranking key is (price? popularity?) or what the counts count, which is the main behavioral unknown. It does correctly add scope context (injectable GLP-1s) beyond the annotations.

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?

A single short sentence with no wasted clauses. It is slightly awkward in word order but front-loads the resource being listed.

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?

For a no-argument read-only list tool this is close to sufficient, but with no output schema the description should say what a row looks like (medication name, formulation, count semantics, rank order). Those remain unexplained, so the agent knows the shape of the call but not the shape of the answer.

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?

There are zero parameters and 100% schema coverage, so there is nothing for the description to disambiguate. Baseline 4 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The sentence identifies the resource (medications GLP-1 Buyer Guide tracks, injectable price list) but relies on the name/title for the verb and is grammatically tangled ("Medications ... keeps a ranked injectable price list for"). It does not state how this differs from siblings find_glp1_prices and find_provider_glp1_prices, so an agent must infer that this returns the taxonomy rather than prices.

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

Usage Guidelines2/5

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

There is no when-to-use guidance and no explicit alternative named. The agent is left to guess that this is the entry point for enumerating medications before calling the price-finding siblings.

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