Skip to main content
Glama

Compare reagent prices

compare_reagent_prices
Read-onlyIdempotent

Batch-compare a reagent purchase list against CacheBy prices. Each item needs a CAS number; optionally pass the price you currently pay (KRW) to get the price difference against CacheBy's cheapest exact match. Useful for quoting an entire experiment's materials.

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": {
      "items": "<items>"
    },
    "name": "compare_reagent_prices"
  }
}

Input Schema

NameRequiredDescriptionDefault
itemsYes

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 readOnly, idempotent, non-destructive, closed-world behavior, so the safety profile is covered. The description adds genuinely useful output semantics — it returns the price difference against CacheBy's cheapest exact match when a current price is supplied — but is silent on handling unmatched CAS numbers, partial failures, and result currency beyond the input KRW.

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?

Three tight sentences, front-loaded with the batch-compare action, then the per-item requirement, then the use case. The final 'Useful for...' sentence is slightly expendable but still earns its place by anchoring intent.

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?

For a batch read tool with no output schema, the description should explain what comes back per item. It covers the headline result (cheapest exact match and the price difference) but leaves gaps: what happens for items with no match, whether brand is used to narrow matching, and the shape of results for a 20-item batch.

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?

Top-level schema coverage is 0% (the 'items' array itself is undescribed), so the description must carry weight, and it does: it states every item needs a CAS number and that currentPrice (KRW) is optional and drives the difference calculation. It does not mention the brand or productName fields or the 20-item batch cap enforced in 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?

'Batch-compare a reagent purchase list against CacheBy prices' names a specific verb, resource, and comparison target, which is clearly distinguishable from siblings like search_by_cas or get_substitutes that look up single items. It does not explicitly name an alternative, so it falls short of full sibling differentiation.

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?

The closing sentence 'Useful for quoting an entire experiment's materials' gives a usage scenario, implying when to reach for it. However, it offers no when-not conditions, no named alternatives (e.g., search_by_cas for single lookups), and no prerequisites such as needing a pre-built purchase list.

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