Skip to main content
Glama

biothings_get_chem

Retrieves detailed chemical compound information by ID such as InChIKey or PubChem CID, including structural and physical properties.

Instructions

Fetch a specific chemical compound by ID (e.g., InChIKey, PubChem CID).

    Retrieves detailed information about a specific chemical compound using its identifier.
    
    **Supported ID formats:**
    - InChIKey: "KTUFNOKKBVMGRW-UHFFFAOYSA-N" (Glucose)
    - PubChem CID: "5793" (Glucose)
    - SMILES: "C([C@@H]1[C@H]([C@@H]([C@H]([C@H](O1)O)O)O)O"
    
    Returns comprehensive chemical information including structural properties, physical properties, 
    chemical properties, stereochemistry information, and chemical identifiers.
    

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
emailNo
fieldsNoall
chem_idYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
idNoChemical identifier (typically InChIKey)
pubchemNoDetailed PubChem information
versionNoVersion number of the data
Behavior3/5

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

No annotations are provided, so the description must fully disclose behavior. It lists the types of information returned (structural, physical, chemical, stereochemistry, identifiers) but does not mention side effects, authentication, rate limits, or error handling. Adequate but not comprehensive.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is front-loaded with the purpose but includes a bullet list of ID formats and return categories that could be more concise. It is somewhat wordy for the value added.

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?

With an output schema existing, return value documentation is covered. However, the description omits details for two parameters (email, fields), making it less complete for a tool with 3 parameters.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%. The description only explains the chem_id parameter with examples, leaving email and fields completely undocumented. This fails to compensate for the lack of 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 verb 'Fetch' and the resource 'specific chemical compound by ID', supported by examples of ID formats. It distinguishes from sibling tools like biothings_get_chems (plural) which imply batch retrieval.

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 single-compound retrieval but does not explicitly state when to use it over alternatives like biothings_query_chems or biothings_get_chems. No exclusions or alternative guidance provided.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/longevity-genie/biothings-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server