Skip to main content
Glama

PeptideCompare.co: US peptide and NAD+ clinic prices

Current peptide promo codes and sales

find_peptide_deals
Read-onlyIdempotent

Promo codes, first-order offers and seasonal sales (Black Friday, Cyber Monday) that US peptide clinics state on their own pages now, each in the clinic's words with the day read. Optionally only clinics that price a given compound.

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

Input Schema

NameRequiredDescriptionDefault
compoundNoOptional. A peptide, NAD+ or a peptide stack, in any common spelling: "NAD+", "BPC-157", "sermorelin", "CJC-1295 / ipamorelin", "GHK-Cu", "Wolverine stack".

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 declare read-only, idempotent, non-destructive and closed-world, so the bar is lower, yet the description adds real context: results come from clinics' own pages, are quoted verbatim in the clinic's words, carry a read date, and reflect what is live now. It stops short of describing result structure or how stale/unreachable pages are handled.

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 tight sentences with no filler, and the core scope (what kinds of offers, which clinics, what freshness) is front-loaded. The compressed phrasing 'with the day read' is slightly awkward but still conveys that each entry carries a date.

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?

With one optional parameter, full schema coverage, rich annotations and no output schema, the description covers the essentials: source, scope, freshness and verbatim quoting. Only the shape of returned entries and empty-result behavior are left implicit, which is a minor gap for a simple read tool.

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 100% and the compound parameter is already richly documented with example spellings, so the baseline is 3. The description adds one meaningful nuance — the filter selects clinics that price the compound rather than deals containing it — but does not clarify whether a non-matching compound yields empty results or unfiltered results.

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 names a specific resource set (promo codes, first-order offers, seasonal sales) scoped to US peptide clinics and sourced from the clinics' own pages, which an agent can distinguish from a pricing tool like find_peptide_prices. It lacks an explicit verb and does not name a sibling, so it falls short of a 5.

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: 'now' and 'current' signal freshness, and the compound clause hints at a filtered view, but there is no explicit statement of when to pick this over find_peptide_prices or get_clinic, and no exclusions or prerequisites.

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