Skip to main content
Glama

NIH PubChem compound lookup by name: PubChem CID, title

health_pubchem_chemical_cid
Read-only

NIH PubChem compound lookup by name (PUG REST): PubChem CID, title, molecular formula, molecular weight and IUPAC name for the best match. Safety and hazard data are not included. One compound per call. Price: $0.002 per successful call, paid with x402 (USDC on Base, Solana and 10 more networks); failed calls are not charged.

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

Input Schema

NameRequiredDescriptionDefault
nameYesCompound name, letters, digits, spaces, commas, hyphens and parentheses, 2 to 100 characters

Output Schema

NameRequiredDescriptionDefault
cidNo
urlNo
queryNo
titleNo
sourceNo
checkedAtNo
iupacNameNo
molecularWeightNo
molecularFormulaNo

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 (readOnlyHint, openWorldHint) already cover the safety profile, yet the description adds substantial context: a per-call price of $0.002 charged via x402 on Base/Solana and ten other networks, that failed calls are free, and that only the best match is returned rather than all matches. It does not state what happens when no match exists, which keeps it short of a 5.

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?

Four sentences, front-loaded with purpose and scope, then exclusions, then cardinality, then pricing. Every sentence carries operational information an agent needs, with no filler.

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 an output schema present, the description needn't enumerate return values, and it still covers scope, cardinality, exclusions, and payment mechanics. The one gap is no-match/error behavior for a lookup tool, which matters for a paid per-successful-call service but is not stated.

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?

Only one parameter exists and the schema already documents it at 100% coverage, including the character set and 2–100 length constraint. The description adds nothing about name format, synonyms, CAS numbers, or case sensitivity beyond the schema, so the baseline 3 applies.

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?

Names a specific verb (liccompound lookup) plus the exact data source (NIH PubChem, PUG REST), the key output (PubChem CID) and the match policy ('best match'). An agent can tell this apart from the many sibling chemical/drug tools (chEMBL, DrugBank, DailyMed) without opening a schema.

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 line 'Safety and hazard data are not included' implicitly steers an agent elsewhere for hazard information, and 'One compound per call' implies one name at a time. But no alternative tool is named and there is no explicit when-to-use/when-not-to-use statement against alternatives like chEMBL or DrugBank, so guidance is only implied.

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