Skip to main content
Glama

PepVault

Search PepVault

search_pepvault
Read-onlyIdempotent

Search PepVault's peptide library, dose guides, vial charts, study summaries, comparisons, glossary and guides. For questions that don't name one compound or term. Returns up to 8 pages with title, URL, type and description.

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

Input Schema

NameRequiredDescriptionDefault
typeNoOnly pages of this type.
queryYesWhat to look for, in plain words ("retatrutide half-life", "how to mix a 5 mg vial").

Output Schema

NameRequiredDescriptionDefault
resultsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare read-only, idempotent, closed-world and non-destructive, so the description's job is to add operational detail — and it does, disclosing a result cap of up to 8 pages. It does not discuss ranking, pagination, or what happens when nothing matches, which keeps it short of full transparency.

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 verb and resource, then scope, then the routing condition and return shape. No filler or repetition of the title.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a two-parameter search tool with full schema descriptions, a complete annotation set, and an output schema, the description covers scope, routing, and result limits. Everything an agent needs to decide to call it and what to expect is present.

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 enum values for 'type' are fully documented in the schema, including usage examples for 'query'. The description adds nothing about parameter behavior, which is acceptable since the schema carries that load.

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 ('Search PepVault's peptide library') and enumerates the content types covered (dose guides, vial charts, study summaries, comparisons, glossary, guides). The sentence 'For questions that don't name one compound or term' separates it from entity-specific siblings like get_peptide and define_term without needing to open their schemas.

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?

Gives a clear selecting condition — use this when the question doesn't name a single compound or term — which implicitly routes named-entity lookups to the sibling tools. It does not name those alternatives explicitly or state any exclusions beyond that, so it falls short of a full when/when-not guide.

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