Skip to main content
Glama

Search review text

search_glp1_reviews
Read-onlyIdempotent

Finds public reviews and Reddit quotes that mention specific words, across every provider and pharmacy on GLP Winner or within one named provider or pharmacy. Example queries include "arrived warm", "refund", "charged twice" and "prior authorization". Returns the newest matches with the provider or pharmacy, source, star rating, date and a short excerpt. Each match records that the words were reported and does not include how often they appear.

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

Input Schema

NameRequiredDescriptionDefault
nameNoProvider or pharmacy whose reviews to search. When omitted, the search covers every provider and pharmacy.
typeNoWhether the name is a telehealth provider, a compounding pharmacy, or "any" for both.any
limitNoHow many matches to return, from 1 to 10.
queryYesWords to find in review text, for example "arrived warm", "refund" or "prior authorization". A match contains every word. "a or b" matches either side. Quotes match an exact phrase. The value is a topic phrase.
sinceNoEarliest review date to include, as YYYY-MM-DD.
max_ratingNoHighest star rating to include, from 1 to 5.
min_ratingNoLowest star rating to include, from 1 to 5.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed7 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 / max_rating / description
      Previous value: -"Only reviews with at most this many stars."New value: +"Highest star rating to include, from 1 to 5."
    • changedInput schema / properties / min_rating / description
      Previous value: -"Only reviews with at least this many stars."New value: +"Lowest star rating to include, from 1 to 5."
    • changedInput schema / properties / name / description
      Previous value: -"Search only this provider’s or pharmacy’s reviews. Omit to search every provider and pharmacy."New value: +"Provider or pharmacy whose reviews to search. When omitted, the search covers every provider and pharmacy."
    • changedInput schema / properties / query / description
      Previous value: -"Words to find in review text, e.g. \"arrived warm\", \"refund\", \"prior authorization\". Every word must appear; use \"a or b\" for either and quotes for an exact phrase. Pass a topic phrase, never personal details about the person."New value: +"Words to find in review text, for example \"arrived warm\", \"refund\" or \"prior authorization\". A match contains every word. \"a or b\" matches either side. Quotes match an exact phrase. The value is a topic phrase."
    • changedInput schema / properties / since / description
      Previous value: -"Only reviews posted on or after this date (YYYY-MM-DD)."New value: +"Earliest review date to include, as YYYY-MM-DD."
    • 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.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so safety is covered. The description adds real value beyond them: results are ordered newest-first, each result carries provider/pharmacy, source, star rating, date and excerpt, and critically each match means "the words were reported" without indicating frequency – an important interpretation limit an agent would otherwise assume wrong.

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?

Three sentences, front-loaded with what the tool does and scoped immediately after, then return shape, then the caveat. The example-query list duplicates the query parameter's schema description, which is the only mildly redundant element.

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 seven-parameter search tool with no output schema, the description supplies the return fields, ordering, and the frequency caveat, which is enough for correct invocation. It falls short only on relationships to the sibling review tool and on how filtering parameters combine with the query.

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 schema already defines name, type, limit, query, since and rating filters in detail. The description only echoes example query strings and the all-vs-one scope, adding little syntax or semantic detail beyond structured fields; baseline 3 applies.

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 opens with a specific verb and resource ("finds public reviews and Reddit quotes") and states the searchable scope (all providers/pharmacies or one named one, plus words to match). It clearly separates itself from provider-lookup siblings by describing text search over review content, though it never names a sibling such as get_glp1_reviews to draw the boundary 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?

Concrete example queries ("arrived warm", "refund", "charged twice", "prior authorization") give the agent a good sense of intended queries, and the closing caveat implies this is for locating mentions rather than counting them. However, there is no explicit statement of when to use this versus get_glp1_reviews, and no excluded use cases beyond the implicit frequency caveat.

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