Skip to main content
Glama

Peptency research library

List compounds

list_compounds
Read-only

Every compound and catalog blend in the library with formula, molecular weight, study count, plus the mechanism and comparison pages.

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": "list_compounds"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

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=true and openWorldHint=false, so the safety profile is covered. The description adds value by disclosing what is returned (formula, MW, study count, mechanism and comparison pages), though it doesn't say anything about result volume, ordering, or pagination for an unfiltered full-library dump.

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 that states scope first and returned fields second, with no filler. The trailing 'plus the mechanism and comparison pages' is slightly vague in phrasing but still earns its place by naming extra return content.

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?

There is no output schema, so the description must carry return-value information, and it does so reasonably by listing the key fields. For a zero-parameter read tool with annotations covering safety, the remaining gap (size/ordering of an unfiltered list) is minor.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters, so there is nothing for the description to disambiguate; baseline 4 applies. The description's implication that all compounds are returned matches the empty schema.

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 the resource (compounds and catalog blends in the library) and enumerates returned attributes (formula, molecular weight, study count), so the agent knows this is a bulk listing. It does not explicitly distinguish itself from get_compound or search_library, leaving the agent to infer the difference from the names alone.

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

Usage Guidelines2/5

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

The word 'Every' implies an unfiltered full listing, which is a useful hint, but there is no explicit when-to-use statement, no exclusion (e.g., 'use get_compound for a single entry'), and no alternative named. Guidance is only implied.

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