Pubchem

Search By Name

search_by_name

Read-onlyIdempotent

Resolve a common chemical or drug name to PubChem CIDs. Use for "what's the CID of ibuprofen?" or to disambiguate. Returns CIDs (Compound IDs) matched to the name. Then use get_compound with the CID for properties.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "name": "ibuprofen"
    },
    "name": "search_by_name"
  }
}

Input Schema

Name	Required	Description	Default
`name`	Yes	Common, IUPAC, or brand name (e.g., "ibuprofen", "caffeine")
`max_results`	No	Cap results (default 5)

Output Schema

Name	Required	Description
`cids`	Yes	List of matching PubChem Compound IDs
`name`	Yes	The chemical/drug name searched
`count`	Yes	Number of CIDs found
`pubchem_urls`	Yes	Direct URLs to PubChem pages for each CID

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedMay 22, 2026

addedInput schema / examples

Added value: +[
+  {
+    "name": "ibuprofen"
+  },
+  {
+    "max_results": 3,
+    "name": "caffeine"
+  }
+]

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "cids": {
+      "description": "List of matching PubChem Compound IDs",
+      "items": {
+        "type": "number"
+      },
+      "type": "array"
+    },
+    "count": {
+      "description": "Number of CIDs found",
+      "type": "number"
+    },
+    "name": {
+      "description": "The chemical/drug name searched",
+      "type": "string"
+    },
+    "pubchem_urls": {
+      "description": "Direct URLs to PubChem pages for each CID",
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "name",
+    "count",
+    "cids",
+    "pubchem_urls"
+  ],
+  "type": "object"
+}

First observedMay 12, 2026

TDQS

A4/5.0

Behavior3/5

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

The description adds minimal behavioral context beyond the annotations. Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint. The description only reiterates that it returns CIDs, which is obvious. No additional traits like authentication or rate limits are mentioned.

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?

The description is concise and well-structured: three sentences covering purpose, usage example, and next step. No unnecessary words or repetition.

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 simple lookup tool with annotations and an output schema, the description is complete. It explains the core function and how to use the result. However, it could briefly mention that results are case-insensitive or that max_results applies, but the schema covers these.

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%, so the baseline is 3. The description provides example values ('ibuprofen', 'caffeine') but does not add significant semantic detail beyond what the schema already provides for name and max_results.

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's purpose: 'Resolve a common chemical or drug name to PubChem CIDs.' This is a specific verb-resource pairing and distinguishes it from siblings like get_compound, which retrieves properties from a CID. The description also provides concrete examples like 'what's the CID of ibuprofen?'.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explicitly guides when to use the tool: 'Use for...to disambiguate.' It also suggests the next step: 'Then use get_compound with the CID for properties.' While it does not list when not to use, the context is clear and sufficient for decision-making.

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

All Pubchem tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.