Skip to main content
Glama

Peptency research library

Get a compound record

get_compound
Read-only

Full record for one compound or blend: chemistry (sequence, formula, weight, CAS, PubChem), mechanism as described in the literature with PMIDs, regulator records, evidence counts and every cited study.

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": {
      "compound": "<compound>"
    },
    "name": "get_compound"
  }
}

Input Schema

NameRequiredDescriptionDefault
compoundYesSlug, name or alias, for example 'retatrutide', 'CJC-1295 no DAC' or 'ghk-cu'

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds useful content-level transparency by disclosing that mechanism data is literature-derived with PMIDs and that evidence counts accompany cited studies, but it says nothing about behavior on a missing or ambiguous compound, nor about response size or rate limits.

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 dense sentence that front-loads the core claim ('Full record for one compound or blend') and then enumerates returned sections in a compact parenthetical list. No filler, though the list is packed enough that it reads more as an inventory than a structured summary.

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 return contents, and it does so thoroughly by naming each section an agent will receive. For a one-parameter read tool with annotations present, the only real gap is behavior on unresolvable compound input.

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?

There is a single required parameter with 100% schema description coverage, including concrete examples ('retatrutide', 'CJC-1295 no DAC', 'ghk-cu'). The description adds no additional meaning about accepted input forms or matching behavior, so the schema is doing all the work; baseline 3 is appropriate.

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?

Names a specific resource (one compound or blend) and enumerates exactly what the returned record contains: chemistry fields, mechanism with PMIDs, regulator records, evidence counts and cited studies. That enumeration implicitly positions it as the aggregate record versus narrower siblings like get_studies or get_regulatory_status, but it never states that contrast outright.

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: the phrase 'full record' suggests this is the tool for comprehensive compound lookup rather than a targeted sub-query. There is no explicit when-to-use guidance, no mention of when to prefer get_studies, get_regulatory_status, or compare_compounds instead, and no stated prerequisites.

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