Skip to main content
Glama

PepVault

Define a peptide term

define_term
Read-onlyIdempotent

Get the glossary entry for a peptide or dosing term (half-life, bacteriostatic water, U-100 syringe, titration): what the word means.

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": {
      "term": "<term>"
    },
    "name": "define_term"
  }
}

Input Schema

NameRequiredDescriptionDefault
termYesThe word or phrase ("half-life", "bacteriostatic water").
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

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so safety and repeatability are covered externally. The description adds that the return is a glossary/meaning entry, which helps set expectations, but it never mentions the max_chars truncation behavior that the schema exposes — relevant since results may be cut short.

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?

A single front-loaded sentence with the key resource first, then examples, then a clarifying gloss. 'What the word means' partially restates 'glossary entry', a small redundancy, but the sentence is efficient overall.

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

Completeness3/5

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

This is a simple two-parameter, fully annotated, schema-documented tool with no output schema, so most requirements are met externally. The one gap is that the definition implies a concise glossary answer while the schema hints at returning page content up to 30,000 characters; that mismatch in expectation is not resolved.

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%, including a description and bounds for max_chars, so baseline is 3. The description's examples clarify what shape of string 'term' expects (a word or short phrase, not an ID), adding modest value beyond the schema, but it says nothing about the truncation 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 ('Get') and resource ('the glossary entry') for a bounded domain ('peptide or dosing term'), reinforced with four concrete example terms. An agent can distinguish this lookup-style tool from peptide-record siblings like get_peptide without opening the schema.

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 parenthetical examples imply when the tool applies (terminology definitions such as half-life or U-100 syringe), which is genuinely useful routing signal. However, there is no explicit statement of when to prefer it over get_peptide, get_page, or search_pepvault, and no exclusion such as 'do not use for compound data'.

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