Skip to main content
Glama

Look up a peptide

peptide_lookup
Read-onlyIdempotent

For questions about one peptide: published dose ranges and protocols, reconstitution, vial sizes, side effects, storage, half-life, FDA status, stacks and community reports. Each dose row carries an origin label (study, regulator, protocol sites, community), sources and page links.

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": {
      "peptide": "<peptide>"
    },
    "name": "peptide_lookup"
  }
}

Input Schema

NameRequiredDescriptionDefault
peptideYesPeptide name, alias or slug, e.g. "BPC-157", "reta", "semaglutide", "CJC-1295 + Ipamorelin".
sectionsNoSections to return. Omit for overview and dosing. Add others as needed, e.g. ["side_effects","community"] or ["storage","reconstitution"].

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 readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds genuine value beyond that by disclosing return structure: each dose row carries an origin label (study, regulator, protocol sites, community), sources and page links, which tells the agent how to weight and cite the data. It does not cover result limits or what happens when a peptide is not found.

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 use case before the content inventory, with no filler or repeated phrasing. The second sentence about provenance labels is the only non-obvious detail and is worth its space; the topic list is dense but each item doubles as a section hint.

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 single-query read tool with a lean two-parameter schema and no output schema, the description covers scope, content categories and the shape of returned dose data. The missing piece is routing: with four related siblings (search, compare, reconstitution and supply calculators) the description never says when to prefer one of them, which is the main residual gap.

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 both parameters are fully documented, including the sections enum and the default to overview and dosing — that sets the baseline at 3. The description's topic list loosely maps onto the section names but adds no syntax, format or validation detail beyond the schema, so no credit above baseline is earned.

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?

"For questions about one peptide" plus an enumeration of covered topics (dose ranges, reconstitution, side effects, storage, half-life, FDA status, stacks, community reports) makes the resource and scope unambiguous. The phrase "one peptide" weakly distinguishes it from peptide_compare and peptide_blend_calculator, but neither sibling is ever named, so the separation is inferred rather than stated.

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?

"For questions about one peptide" implies the selection condition, and the topic list hints at what falls inside scope. However, there is no explicit when-not guidance and no named alternatives — an agent asking about a peptide plus a mixing ratio could reasonably land on peptide_reconstitution_calculator or peptide_search instead, and nothing here resolves that.

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