Skip to main content
Glama

Toolcall

by click.toolcall

chem-safety

Full safety profile for any chemical by CAS number or name: GHS hazard classification (signal word, pictograms, H-statements, P-codes), first-aid measures for inhalation/skin/eye/ingestion, fire-fighting guidance, UN transport number, PPE, and CAMEO reactivity profile. Sourced live from PubChem (NIH) authoritative annotations. JSON response. [Paid: $0.03 USDC per call via x402 on Base; the calling client pays automatically.]

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
casNoCAS registry number, e.g. 7681-52-9
nameNoChemical name, alternative to cas

TDQS

A3.7/5.0
Behavior3/5

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

The description discloses data source (PubChem live), response format (JSON), and payment information ($0.03 USDC per call). However, with no annotations, it fails to clarify that at least one parameter is required despite the schema allowing both to be optional.

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?

The description is front-loaded with the main purpose and lists contents concisely. It is slightly verbose with the full enumeration but remains clear and well-structured.

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?

The description covers all major aspects of the tool: input parameters, output contents, data source, and pricing. Given no output schema, it provides sufficient context for an agent to judge suitability.

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 description adds 'by CAS number or name' which reinforces the two optional parameters. No additional format constraints or examples are provided beyond the schema descriptions.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool provides a full safety profile for chemicals by CAS number or name, listing all included components (GHS classification, first-aid, etc.). It distinguishes itself from siblings like chem-compat by specifying the exact safety data provided.

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 description implies use when needing a chemical safety profile but does not explicitly state when to use this tool vs alternatives. No when-not-to-use guidance or comparison to siblings like chem-compat is provided.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Toolcall toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.9/5.0
Disambiguation5/5

Each of the 30 tools has a highly specific, non-overlapping purpose, from brand visibility to chemical safety to YouTube transcripts. Descriptions are detailed and clearly differentiate each tool's function, eliminating ambiguity.

Naming Consistency4/5

All tool names use lowercase with hyphens, creating a consistent visual pattern. However, the structure varies: some are noun-verb (email-validate, pdf-extract), others noun-noun (brand-visibility, chem-compat). This minor inconsistency prevents a perfect score.

Tool Count3/5

With 30 tools, the server offers a very broad surface. While each tool earns its place as a distinct utility, the high count may overwhelm agents and dilute focus. It is borderline heavy for a single server, hence a score of 3.

Completeness3/5

The tool set covers a wide range of domains: business, chemicals, crypto, domain, email, finance, holidays, trade, jobs, legal, mapping, medical, news, packages, electronics, PDF, product, recall, sanctions, screenshots, SEC, tech stack, web archive, web search, YouTube. Yet it lacks some common utilities like weather, translation, or image analysis, leaving notable gaps for a general-purpose utility server.

Resources