Skip to main content
Glama

List compounds

list_compounds
Read-onlyIdempotent

List the compounds Amino Desk covers, with evidence grade (A strongest to D weakest), US legal status and a one-line summary. All filters are optional.

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
goalNoWhat the compound is promoted for
gradeNoEvidence grade
legal_laneNoLegal status group

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/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 a closed-world scope, so safety is fully covered structurally. The description adds useful output detail (grade scale, legal status, one-line summary) but says nothing about result size, pagination, ordering of the list, or truncation behavior for a catalog tool.

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 sentences, no filler, and the payload description is front-loaded ahead of the optional-filter note. Every clause contributes information the agent cannot get from the name alone.

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 simple, annotation-covered, read-only list tool with no output schema, the description is sufficient: the agent knows what it returns and that filters may be omitted. The only gap is result volume/ordering behavior, which matters mildly for a list endpoint but is not blocking.

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?

Schema coverage is 100%, so baseline would be 3, but the description adds genuine meaning beyond the schema: it explains the grade ordering (A strongest to D weakest) where the schema only says "Evidence grade", and clarifies that legal status is US-specific while the enum field is just "Legal status group". The goal parameter's meaning is already fully carried by the 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?

States a specific verb and resource ("List the compounds Amino Desk covers") and names the exact fields returned: evidence grade, US legal status, one-line summary. It doesn't explicitly contrast with the get_compound sibling, but the plural list framing plus returned fields makes the distinction inferable. Slightly short of a 5 because no sibling is named.

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?

"All filters are optional" tells the agent the tool can be called with no arguments to enumerate everything, which is real usage context. However, there is no explicit guidance on when to use this versus get_compound or search, and no stated preference for filtering versus listing all.

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