Skip to main content
Glama

Peptency research library

Compare two compounds

compare_compounds
Read-only

Side by side chemistry, class, mechanism statements, regulator records and study counts for two compounds, with the comparison page when one exists.

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": {
      "a": "<a>",
      "b": "<b>"
    },
    "name": "compare_compounds"
  }
}

Input Schema

NameRequiredDescriptionDefault
aYesFirst compound
bYesSecond compound

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.1/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 safety is covered; the description adds the useful content scope of what is compared. It says nothing about what happens when a compound is unknown, ambiguity in name resolution, or how the optional "comparison page" affects the result.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

One compact sentence with no filler, and the core comparison intent is front-loaded. However, the telegraphic opening ("Side by side chemistry, class, ...") reads as a fragment and the trailing page clause is tacked on without structure.

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?

With no output schema, the description carries the burden of describing return values; it does list the compared dimensions, which is the main thing an agent needs. It omits result shape, handling of missing/unmatched compounds, and what the "comparison page" reference actually returns, leaving gaps for a read tool whose output is otherwise undocumented.

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% with two required string parameters "a" and "b" already documented as "First compound"/"Second compound". The description confirms the two-compound framing but adds no detail on expected identifier format or name-matching behavior, so the baseline 3 applies.

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?

"Side by side ... for two compounds" makes the comparative intent clear and the enumerated dimensions (chemistry, class, mechanism statements, regulator records, study counts) tell an agent what the comparison covers, distinguishing it from get_compound. The elliptical phrasing lacks a verb and never names the single-compound sibling explicitly, so it is clear but not maximally differentiated.

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?

There is no when-to-use guidance: nothing says to prefer this over calling get_compound twice, nor when the plain comparison fails. The trailing clause "with the comparison page when one exists" hints at a conditional behavior without explaining what an agent should do with that.

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