Skip to main content
Glama

Get a compound entry

get_compound
Read-onlyIdempotent

Get Amino Desk's full entry for one compound as Markdown: what it is, human evidence, US legal status, label or reported dosing with its source, safety and sources.

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

Input Schema

NameRequiredDescriptionDefault
slugYesCompound slug or name, such as semaglutide, bpc-157 or Tirzepatide

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/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, and closed-world behavior. The description adds useful context beyond that: the response is Markdown and includes sourcing for dosing, safety, and legal-status claims, which helps the agent understand output shape and trust signals.

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?

It is a single front-loaded sentence that leads with the action and resource, followed by the content list. The enumerated sections are dense but each contributes to setting expectations for the returned Markdown.

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?

For a one-parameter read tool with no output schema, the description adequately covers the return format and content categories. It does not mention not-found or error behavior, but otherwise gives the agent enough to call it correctly.

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%, and the schema already explains the slug or name parameter with examples. The description adds only that the entry concerns a single compound, so the schema continues to carry the parameter semantics.

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 uses a specific verb/resource combination ('Get ... full entry for one compound') and enumerates the entry contents, so the agent knows exactly what this returns. It does not explicitly differentiate itself from siblings like list_compounds or search, which keeps it just below a 5.

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 implied by 'one compound' and the sibling list, but the description never states when to choose this over list_compounds or search, nor any exclusions. It is adequate but leaves the routing decision to inference.

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