Skip to main content
Glama

Search by CAS numbers

search_by_cas
Read-onlyIdempotent

Look up CacheBy products for multiple CAS registry numbers at once (e.g. from a paper's materials list). Returns matching products per CAS number with prices in KRW.

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": {
      "casNumbers": "<casNumbers>"
    },
    "name": "search_by_cas"
  }
}

Input Schema

NameRequiredDescriptionDefault
casNumbersYesCAS registry numbers, e.g. ["67-68-5", "7647-14-5"]

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is covered. The description adds that results are grouped per CAS number and priced in KRW, which is useful since there is no output schema, but it says nothing about behavior when a CAS number has no match.

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 with zero filler, and the batch scope plus target resource are front-loaded before the return-value note. Every clause carries information.

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 single-parameter read-only lookup with full schema coverage and rich annotations, the description covers purpose, input source, and return shape (per-CAS grouping, KRW prices). Only partial-result handling for unmatched CAS numbers is unaddressed.

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% and the single parameter already documents the array, its examples, and the 1–20 bounds. The description reinforces batch semantics ('multiple ... at once'), but adds no format, validation, or normalization rules beyond what the schema states.

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 ('Look up CacheBy products') plus a scope qualifier ('for multiple CAS registry numbers at once') that separates it from a generic product search. It does not explicitly name or contrast with search_products, so the differentiation is implicit rather than stated.

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 parenthetical '(e.g. from a paper's materials list)' gives a concrete usage context, which implies when this tool fits. There is no guidance on when not to use it and no pointer to siblings like search_products for single-term queries.

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