Skip to main content
Glama
Augmented-Nature

Unofficial PubChem MCP Server

get_external_references

Retrieve external database links for PubChem compounds to access related information in ChEMBL, DrugBank, KEGG, and other resources.

Instructions

Get links to external databases (ChEMBL, DrugBank, KEGG, etc.)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
cidYesPubChem Compound ID (CID)

Implementation Reference

  • The main handler function for executing the 'get_external_references' tool logic. Currently a placeholder returning 'not yet implemented' message.
    private async handleGetExternalReferences(args: any) {
      return { content: [{ type: 'text', text: JSON.stringify({ message: 'External references not yet implemented', args }, null, 2) }] };
    }
  • Input schema definition for the 'get_external_references' tool, specifying the required 'cid' parameter.
    inputSchema: {
      type: 'object',
      properties: {
        cid: { type: ['number', 'string'], description: 'PubChem Compound ID (CID)' },
      },
      required: ['cid'],
    },
  • src/index.ts:685-695 (registration)
    Tool registration entry in the tools array passed to server.setTools(), including name, description, and schema.
    {
      name: 'get_external_references',
      description: 'Get links to external databases (ChEMBL, DrugBank, KEGG, etc.)',
      inputSchema: {
        type: 'object',
        properties: {
          cid: { type: ['number', 'string'], description: 'PubChem Compound ID (CID)' },
        },
        required: ['cid'],
      },
    },
  • src/index.ts:802-803 (registration)
    Switch case in the request handler that dispatches calls to the 'get_external_references' handler method.
    case 'get_external_references':
      return await this.handleGetExternalReferences(args);
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states the tool 'Get links' but does not describe what the output looks like (e.g., list of URLs, structured data), whether it's a read-only operation, potential rate limits, or error handling. For a tool with no annotations, this leaves significant gaps in understanding its behavior and constraints.

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 a single, efficient sentence that front-loads the core purpose without unnecessary words. It uses parentheses to include examples (ChEMBL, DrugBank, KEGG, etc.) concisely. Every part of the sentence contributes directly to understanding the tool's function, making it appropriately sized and well-structured.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's complexity (a read operation with one parameter) and the lack of annotations and output schema, the description is incomplete. It does not explain the return format, potential limitations (e.g., which databases are supported), or error cases. For a tool that retrieves external data, more context is needed to guide effective use, especially without structured output information.

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?

The input schema has 100% description coverage, with the parameter 'cid' documented as 'PubChem Compound ID (CID)'. The description adds no additional parameter semantics beyond implying that 'cid' is used to fetch external references. Since schema coverage is high, the baseline score is 3, as the description does not compensate with extra details like format examples or validation rules.

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

Purpose4/5

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

The description clearly states the verb 'Get' and the resource 'links to external databases', specifying examples like ChEMBL, DrugBank, and KEGG. It distinguishes this tool from siblings focused on analysis, prediction, or searching by indicating it retrieves external references. However, it does not explicitly differentiate from 'get_literature_references' or 'get_assay_info', which might also involve external links, leaving some ambiguity.

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternatives. It does not mention prerequisites, such as needing a PubChem CID, or specify scenarios where this is preferred over other 'get_' tools like 'get_compound_info' or 'get_literature_references'. Without explicit when-to-use or exclusion criteria, the agent must infer usage from the purpose alone.

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/Augmented-Nature/Augmented-Nature-PubChem-MCP-Server'

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