Skip to main content
Glama

Find a provider or pharmacy by name

find_glp1_provider_or_pharmacy
Read-onlyIdempotent

Looks up a telehealth provider or compounding pharmacy on GLP Winner by name, including misspellings and partial names. Returns each match’s type (provider or pharmacy), rating, whether GLP Winner lists its prices or only its reviews, and links. A provider with listed prices includes links.getStarted, its sign-up URL.

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": {
      "query": "<query>"
    },
    "name": "find_glp1_provider_or_pharmacy"
  }
}

Input Schema

NameRequiredDescriptionDefault
typeNoWhether the name is a telehealth provider, a compounding pharmacy, or "any" for both.any
limitNoHow many matches to return, from 1 to 10.
queryYesProvider or pharmacy name, or part of a name. Misspellings are included in the matches.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • changedInput schema / properties / limit / description
      Previous value: -"How many matches to return (1-10)."New value: +"How many matches to return, from 1 to 10."
    • changedInput schema / properties / query / description
      Previous value: -"The name to look up: a provider, a pharmacy, or part of one. Misspellings are tolerated."New value: +"Provider or pharmacy name, or part of a name. Misspellings are included in the matches."
    • changedInput schema / properties / type / description
      Previous value: -"Whether the name is a telehealth provider or a compounding pharmacy; \"any\" when unsure."New value: +"Whether the name is a telehealth provider, a compounding pharmacy, or \"any\" for both."
  2. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare this as a safe, idempotent, closed-world read, so the bar is lower. The description still adds real value by describing the shape of the response: each match's type, rating, whether prices or only reviews are listed, and links, plus the conditional detail that a provider with listed prices includes links.getStarted.

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?

Two sentences, front-loaded with the primary action before the return-shape detail. The second sentence is dense but every clause carries useful information about what to expect back.

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 does partial duty on return values by naming the key fields and the conditional getStarted link. It omits what happens on zero matches, result ordering, and how limit interacts with scoring, which would matter for a fuzzy-match tool returning ranked candidates.

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 the baseline is 3. The description's notes on misspellings and partial names essentially restate what the schema already says for the query parameter, and it adds nothing about the limit or ordering behavior.

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 gives a specific verb and resource: looks up a telehealth provider or compounding pharmacy by name, with fuzzy matching on misspellings and partial names. It is clear what the tool does, but it never distinguishes itself from the similarly named sibling search_glp1_providers, so an agent must open both schemas to choose.

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 'look up by name, including misspellings and partial names' framing, which suggests a fuzzy name-resolution scenario. There is no explicit when-to-use or when-not-to-use statement and no pointer to alternatives such as get_glp1_provider for a known single entity or search_glp1_providers.

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