Skip to main content
Glama

PepVault

Get a PepVault page

get_page
Read-onlyIdempotent

Get a pepvault.app reference page by its path or URL (for example /guides/where-to-inject-peptides), as its published Markdown. It reads the reference pages listed on pepvault.app, not the pages about the PepVault app.

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

Input Schema

NameRequiredDescriptionDefault
pathYesA pepvault.app path ("/peptides/bpc-157") or URL.
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.6/5.0
Behavior3/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 safety is covered. The description adds that output is published Markdown and that only reference pages are read, but says nothing about error handling, missing paths, or truncation behavior (left to the schema).

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?

Two tight sentences with the primary action and example up front, followed by the scope clarification. No filler or redundancy.

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 complete schema and annotation coverage, the description supplies the essential purpose and scope. Only minor gaps remain around failure modes and whether content is paginated beyond max_chars.

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 path and max_chars are already documented, including the 2000–30000 range and default. The description only restates the path-or-URL flexibility and adds a sample path, which is marginal added meaning.

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 gives a specific verb and resource ("Get a pepvault.app reference page"), an example path, and the return format ("published Markdown"). It also scopes the resource by excluding app-related pages, though it does not contrast with siblings like get_peptide or get_study.

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 implied by the path/URL phrasing and the exclusion of app pages, but there is no explicit statement of when to prefer this over get_peptide, get_study, or search_pepvault. The agent must infer the choice from the resource names alone.

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