Skip to main content
Glama

PepVault

Get a peptide's dose guide

get_dose_reference
Read-onlyIdempotent

Get one compound's Dose Guide page: the dose ranges studies used, how often, and a typical run length. For questions about dosing amounts or schedules. These are research ranges, never a dose for a person.

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_dose_reference"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesThe compound's name, a brand name or an alias.
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

A4.2/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 meaningful context beyond them: the data is a research range, 'never a dose for a person,' which sets expectation about the output's nature and limits liability-style misuse.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three short sentences, front-loaded with the resource and payload, followed by the use case and the safety caveat. No redundant or filler 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 simple two-parameter read tool with full annotations and full schema coverage, the description covers purpose, content and usage. Minor gaps remain around behavior for unknown compounds and truncation when max_chars is set, but nothing critical for correct invocation is missing.

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%, so both parameters (name, max_chars) are already documented in the schema. The description only implies that 'name' identifies a single compound; it adds no format or alias guidance and says nothing about truncation via max_chars.

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?

States a specific verb and resource ('Get one compound's Dose Guide page') and enumerates the returned content (dose ranges, frequency, run length). This is clearly distinguishable from siblings like get_peptide or get_page.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Adds an explicit use condition: 'For questions about dosing amounts or schedules.' It does not name an alternative tool or state when not to use it, but the routing signal is clear.

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