Skip to main content
Glama

Bluedose GLP-1 Tools

GLP-1 search interest by country

glp1_search_interest

Average monthly Google searches for Mounjaro, Ozempic, Wegovy, Zepbound, Saxenda, tirzepatide and semaglutide in a country (ISO code, e.g. US, BR, JP), from Bluedose's open dataset (Google Keyword Planner, Nov 2026). Searches show interest, not prescriptions.

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": {
      "country": "<country>"
    },
    "name": "glp1_search_interest"
  }
}

Input Schema

NameRequiredDescriptionDefault
countryYesISO 3166-1 alpha-2 code

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior3/5

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

With no annotations, the description carries the full burden and does supply useful provenance (Bluedose open dataset, Google Keyword Planner, Nov 2026 snapshot) plus a clear semantic limitation that the figures measure interest, not prescriptions. It does not disclose the return shape (single number vs. per-drug breakdown), the unit/scale of 'average monthly searches', or what happens for countries outside dataset coverage.

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?

The core metric and scope are front-loaded in the first clause, and the closing caveat is one short sentence that earns its place by preventing misuse of the data. The long inline list of seven drug names is justified by the need to define coverage, though the parenthetical source/date could be trimmed slightly.

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 one-parameter lookup with no annotations and no output schema, the description covers the metric, data source, timeframe, and interpretation caveat reasonably well. The notable remaining gap is what the response actually contains — whether one aggregate figure or a per-drug series — which no structured field supplies.

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?

Schema coverage is 100% and the schema already defines the single parameter as an ISO 3166-1 alpha-2 code, so the baseline is 3. The description adds concrete examples (US, BR, JP) that reinforce the expected format and casing, which is modest but genuine added value for the only parameter.

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 precise metric (average monthly Google searches), enumerates the exact drug terms covered (Mounjaro, Ozempic, Wegovy, Zepbound, Saxenda, tirzepatide, semaglutide), and scopes it to a country. The sibling tools (next_injection_site, shot_day_countdown) are on unrelated topics, so an agent can distinguish this tool 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?

There is no explicit when-to-use statement, no named alternative, and no exclusion criteria; usage is only implied by the metric itself. The closing caveat 'Searches show interest, not prescriptions' guides interpretation of results rather than selection of the tool, so it does not raise this above implied guidance.

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