Skip to main content
Glama
Augmented-Nature

Unofficial PubChem MCP Server

get_regulatory_info

Retrieve regulatory compliance data from FDA, EPA, and international agencies for chemical compounds using PubChem Compound IDs.

Instructions

Get regulatory information from FDA, EPA, and international agencies

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
cidYesPubChem Compound ID (CID)

Implementation Reference

  • The main handler function for the 'get_regulatory_info' tool. It currently returns a placeholder message indicating that regulatory info is not yet implemented.
    private async handleGetRegulatoryInfo(args: any) {
      return { content: [{ type: 'text', text: JSON.stringify({ message: 'Regulatory info not yet implemented', args }, null, 2) }] };
    }
  • src/index.ts:798-799 (registration)
    The switch case in the CallToolRequestSchema handler that dispatches calls to the 'get_regulatory_info' tool to its handler function.
    case 'get_regulatory_info':
      return await this.handleGetRegulatoryInfo(args);
  • src/index.ts:672-682 (registration)
    The tool registration entry in the ListToolsRequestSchema response, including name, description, and input schema.
    {
      name: 'get_regulatory_info',
      description: 'Get regulatory information from FDA, EPA, and international agencies',
      inputSchema: {
        type: 'object',
        properties: {
          cid: { type: ['number', 'string'], description: 'PubChem Compound ID (CID)' },
        },
        required: ['cid'],
      },
    },
  • The input schema definition for the 'get_regulatory_info' tool, specifying a required 'cid' parameter.
    inputSchema: {
      type: 'object',
      properties: {
        cid: { type: ['number', 'string'], description: 'PubChem Compound ID (CID)' },
      },
      required: ['cid'],
    },
Behavior2/5

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

No annotations are provided, so the description carries full burden. It states the tool retrieves information but doesn't disclose behavioral traits such as data freshness, rate limits, authentication needs, or potential side effects. This is a significant gap for a tool with no annotation coverage.

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 with zero waste. It is appropriately sized and front-loaded, clearly stating the tool's purpose without unnecessary elaboration.

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 no annotations and no output schema, the description is incomplete. It doesn't explain what the tool returns (e.g., format, structure of regulatory info) or address complexity like data sources or limitations, leaving gaps for effective agent use.

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 description coverage is 100%, so the schema already documents the 'cid' parameter as a PubChem Compound ID. The description adds no additional parameter details beyond what the schema provides, resulting in a baseline score of 3.

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 action ('Get') and resource ('regulatory information'), specifying the sources (FDA, EPA, international agencies). It distinguishes from siblings like get_safety_data or get_toxicity_info by focusing on regulatory aspects rather than general safety/toxicity, though the distinction could be more explicit.

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?

No explicit guidance on when to use this tool versus alternatives like get_safety_data or get_toxicity_info, which might overlap. The description implies usage for regulatory data but doesn't specify prerequisites, exclusions, or comparative contexts with sibling tools.

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