Skip to main content
Glama

Find substitutes

get_substitutes
Read-onlyIdempotent

Find substitute products on CacheBy for a reagent by CAS number — same substance from other brands/specs, sorted by price ascending. Use when a product is out of stock or to find a cheaper equivalent. To get a product page URL, call search_products with the partNumber.

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": {
      "casNumber": "<casNumber>"
    },
    "name": "get_substitutes"
  }
}

Input Schema

NameRequiredDescriptionDefault
casNumberYesCAS registry number of the reagent
excludeProductIdNoProduct id to exclude (the one being replaced)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the description's job is to add context — and it does, disclosing the price-ascending sort order and that results are same-substance alternatives from other brands/specs. It says nothing about result caps or pagination, so an agent cannot tell how large a result set to expect.

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?

Three short sentences, each doing distinct work: what it returns and how it's ordered, when to use it, and where to go for a related need. Front-loaded and free of restatement.

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?

With no output schema, the description partially compensates by naming the sort order and the nature of the results, which is the key unknown for this tool. The remaining gap is the actual returned fields and any result-count limits, which an agent would still have to discover empirically.

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%, so both parameters are already documented, establishing a baseline of 3. The description reinforces that casNumber keys the search on substance identity and implies excludeProductId is the product being replaced, but adds no format, validation, or edge-case guidance beyond 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?

Names a specific verb and resource ('Find substitute products on CacheBy for a reagent by CAS number') and defines the result set precisely ('same substance from other brands/specs, sorted by price ascending'). It stops short of explicitly contrasting with the close siblings get_similar_products and compare_reagent_prices, so an agent still has to reason about which one to pick.

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

Usage Guidelines4/5

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

Gives concrete trigger conditions: 'when a product is out of stock or to find a cheaper equivalent.' It also routes to a sibling for a related need ('To get a product page URL, call search_products with the partNumber'). No exclusion rules for the overlapping similar/pricing tools are stated.

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