Skip to main content
Glama

PepBank Peptide Research MCP: BPC-157, Retatrutide and Tirzepatide Studies and Trials

Search publications

search_publications
Read-onlyIdempotent

Return stored papers with citation identifiers and extraction status. Use this for paper discovery, publication dates or unchecked coverage. Use search_findings instead for checked claims and source sentences, or get_peptide_brief for a peptide overview. extraction_status identifies the layer: extracted is layer 1 with checked findings. queued and stored_only are layer 2 without checked findings. Layer 2 results carry contains_unchecked_papers. Abstract text appears only when the article license allows it. design_hint is an unchecked PubMed publication-type tag. profile describes the checked findings of a paper: evidence classes, designs, species and peptide roles.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "search_publications"
  }
}

Input Schema

NameRequiredDescriptionDefault
qNoFree-text query. Words are combined with AND. Example: tendon healing.
sortNorelevance (default with q), newest (default), oldest, cited or evidence.
viewNoDefault compact.
limitNoDefault 10. Max 25 compact, 10 full.
cursorNoOpaque cursor from next_cursor of the previous page. Send the same filters again.
designNoFilter by design_hint: the PubMed publication-type tag of the paper, not checked. One of meta_analysis, systematic_review, rct, clinical_trial, observational, case_report, review, animal, in_vitro, preprint, other. For the design of the checked findings, read profile in the results.
statusNoPublication status, for example retracted.
peptideNoPeptide name, alias, slug or ID. Examples: BPC-157, semaglutide, PEP-000001.
as_of_seqNoRead the data as it was at this data_seq. Use it to reproduce an earlier answer.
open_accessNoOnly open-access papers when true.
published_toNoLast publication year.
published_fromNoFirst publication year.
primary_subjectNoOnly papers where the peptide is a main subject (title or MeSH).
extraction_statusNoextracted = layer 1 (checked findings). queued or stored_only = layer 2 (not checked).

Output Schema

NameRequiredDescriptionDefault
resultsNoRows.
next_cursorNoNext page.
total_countNoTotal.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds real value beyond that: the layer 1 vs layer 2 model, the contains_unchecked_papers flag on layer 2 results, and the licensing constraint on abstract text. It is capped at 3 because it never states pagination or result-size behavior, which is left entirely 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.

Conciseness4/5

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

Purpose and scope are front-loaded, then alternatives, then a compact glossary of result fields. Every sentence carries semantics, though the field glossary runs long enough that an agent skimming for invocation guidance must read past several result-oriented sentences.

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?

This is a broad, 14-parameter search tool with a rich output schema, yet the description still supplies the interpretive layer an agent needs to read results correctly: what extraction_status values mean, why design_hint is not a verified design, and when abstract text is absent. Nothing essential for correct invocation is omitted.

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 description coverage is 100%, so the baseline is 3 and every parameter is already documented. The description adds interpretation rather than new parameter detail: it explains that extraction_status encodes layer membership and warns that design_hint is an unchecked PubMed tag while profile carries the checked-finding design. That is useful but does not extend to the 14 parameters individually.

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?

The first sentence names a specific verb and resource plus the two things it returns: stored papers with citation identifiers and extraction status. It immediately distinguishes itself from search_findings and get_peptide_brief by naming the alternative each time.

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

Usage Guidelines5/5

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

It gives explicit when-to-use triggers (paper discovery, publication dates, unchecked coverage) and routes two competing needs to named siblings: checked claims and source sentences to search_findings, peptide overviews to get_peptide_brief. An agent has no inference left to do.

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.