Skip to main content
Glama

PepVault

Get a study summary

get_study
Read-onlyIdempotent

Get one study summary: what the study tested, how it was done, what it found, its limits and the takeaway. Takes the study's slug, its pepvault.app URL or its PubMed id.

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

Input Schema

NameRequiredDescriptionDefault
idYesThe study's slug ("bpc-157-chang-2011"), its pepvault.app URL, or its PubMed id.
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.8/5.0
Behavior4/5

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

Annotations already establish read-only, idempotent, non-destructive, closed-world behavior, so the description need not restate safety. It adds useful return-content detail (tested, methods, findings, limits, takeaway), though it says nothing about truncation behavior tied to max_chars or what happens when an ID 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.

Conciseness5/5

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

Two front-loaded sentences with no filler: the first says what the tool returns, the second says how to identify the study. The content list is compact and skimmable.

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?

With no output schema, the description must explain the return shape, and it does list the summary sections an agent will receive. It is nearly complete for a two-parameter read-only tool, but leaves the max_chars truncation/error behavior to the schema.

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 the id and max_chars semantics are already documented; the description repeats the accepted identifier forms (slug, URL, PubMed id) but adds no format details or examples beyond the schema. It omits any mention of max_chars, leaving the schema to carry that parameter.

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?

States a specific verb and resource ('Get one study summary') and enumerates the summary's sections, so the agent knows this returns a single study rather than a list. It does not explicitly name list_studies or search_pepvault, so sibling differentiation is implicit 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?

The phrase 'one study summary' implies use when a single study is needed, but there is no explicit when-to-use/when-not guidance or routing to list_studies, search_pepvault, or get_page. The agent must infer the boundary from the name and scope.

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