Skip to main content
Glama

PepVault

Compare two peptides

compare_peptides
Read-onlyIdempotent

Get PepVault's side-by-side page for two compounds (for example BPC-157 and TB-500): how they differ and which does what. When no comparison page exists it returns each compound's page link.

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": {
      "a": "<a>",
      "b": "<b>"
    },
    "name": "compare_peptides"
  }
}

Input Schema

NameRequiredDescriptionDefault
aYesThe first compound.
bYesThe second compound.
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 declare readOnly, idempotent, non-destructive, and closed-world, so the safety profile is covered. The description adds genuinely new behavioral context by disclosing the fallback path: when no comparison page exists, it returns each compound's page link instead. It does not mention truncation behavior, but that is documented in 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 behavior front-loaded and the fallback case second. The example is compact and earns its place by clarifying what counts as a compound; there is no filler.

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 carries the burden of explaining returns, and it does so at a high level: a side-by-side page, or page links as a fallback. For a simple two-argument read tool this is nearly complete, with only the truncation/format details left 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 description coverage is 100%, so all three parameters are already documented, including the max_chars range and default. The description only reinforces that a and b are compounds via the BPC-157/TB-500 example and adds no syntax or format detail beyond the schema, so the baseline 3 applies.

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 names a specific verb and resource: it fetches PepVault's side-by-side comparison page for two compounds, with a concrete example (BPC-157 and TB-500) and the payload ('how they differ and which does what'). It implicitly separates itself from the single-compound get_peptide sibling, though it never names that sibling explicitly.

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 only implied: an agent can infer this is the tool for comparing two compounds rather than fetching one. There is no explicit statement of when to prefer this over get_peptide or search_pepvault, and no prerequisites or exclusions are given.

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