sds-mcp-server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_sds_by_nameA | Search for Safety Data Sheets (SDS) by chemical or product name. Args: chemical_name: Chemical or product name to search for, e.g. "Acetone". is_contains: If True, match names containing this text instead of requiring an exact match (useful for partial or misspelled names). include_synonyms: If True, also match known synonyms of the chemical name. limit: Maximum number of results to return (the source can return 100+ matches for common chemicals, so this keeps responses manageable). Returns: A list of matching records, each with: id, product_name, manufacturer, cas_number, msds_number, revision_date, has_sds, and sds_url (a direct link to the SDS document, usually a PDF). |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 1 tool
Only one tool exists, so there is no possibility of ambiguity or overlap. The tool's purpose is clearly defined as searching for SDS by chemical or product name.
The single tool name 'search_sds_by_name' is consistent with a clear verb_noun pattern and clearly indicates its function. There are no other tools to conflict with.
With only one tool, the server feels thin for a domain that could reasonably include fetching by ID or listing all SDS. However, for a focused search-only server, a single tool may be acceptable, so this is borderline.
The tool provides comprehensive search options (exact, partial, synonyms, limit) and returns useful metadata including a direct URL to the SDS. Gaps include lack of direct retrieval by ID or pagination beyond a simple limit, but the core search use case is well covered.