Skip to main content
Glama

PepVault

Get a peptide's reference page

get_peptide
Read-onlyIdempotent

Get one compound's reference page: what it is, the dose range studies used, how often, half-life, side effects and how strong the evidence is. Takes a peptide's or GLP-1's name; brand names and aliases work (Ozempic and Wegovy open semaglutide).

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

Input Schema

NameRequiredDescriptionDefault
nameYesThe compound's name, a brand name or an alias ("BPC-157", "Ozempic", "tirzepatide").
max_charsNoReturn at most this many characters of the page (2000–30000; default the whole page up to 30000).

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 cover the safety profile (readOnlyHint, idempotentHint, destructiveHint=false, openWorldHint=false), so the bar is lower, and the description still adds real behavior: it discloses what the page contains and that brand/alias inputs are resolved to the underlying compound ("Ozempic and Wegovy open semaglutide"). It does not say what happens on an unresolved name or how the page is truncated, which keeps it below a 5.

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 purpose followed by input guidance, with no filler. The second sentence partially duplicates the schema's `name` description, which is the only wasted wording.

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 2-parameter read with full schema coverage and annotations, the description covers purpose, alias resolution, and what the returned page includes in lieu of an output schema. The only unchecked box is `max_chars` behavior (what truncation means for the agent), which the schema documents adequately.

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?

With 100% schema description coverage, the schema already defines both `name` (with alias/brand examples) and the `max_chars` range. The description's alias note largely restates the schema and it says nothing about `max_chars` or truncation behavior, so it adds only marginal meaning beyond structured data.

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?

"Get one compound's reference page" pairs a specific verb with a specific resource, and the enumeration (dose range, frequency, half-life, side effects, evidence strength) makes the payload concrete. It stops short of naming a contrast with siblings like get_dose_reference or compare_peptides, so an agent must infer that this is the whole-compound overview rather than a focused dose or comparison tool.

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?

Implicit context is present: it says to supply a peptide or GLP-1 name and that brand names and aliases resolve to the compound, which tells the agent this is the lookup entry point. There is no explicit when-to-use-this-vs-alternative statement, no mention of search_pepvault for unknown names or get_dose_reference for dosing tables, and no stated 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