Skip to main content
Glama
Augmented-Nature

PubChem MCP Server

get_regulatory_info

Retrieve regulatory data from FDA, EPA, and international agencies by inputting a PubChem Compound ID (CID). Access safety and compliance details for chemical compounds.

Instructions

Get regulatory information from FDA, EPA, and international agencies

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
cidYesPubChem Compound ID (CID)

Implementation Reference

  • The handler function that implements the core logic of the get_regulatory_info tool. Currently a placeholder indicating the feature 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) }] };
    }
  • The input schema defining the parameters for the get_regulatory_info tool (requires 'cid').
    inputSchema: {
      type: 'object',
      properties: {
        cid: { type: ['number', 'string'], description: 'PubChem Compound ID (CID)' },
      },
      required: ['cid'],
    },
  • src/index.ts:672-682 (registration)
    Registration of the tool in the ListToolsRequestSchema handler, including name, description, and 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'],
      },
    },
  • src/index.ts:798-799 (registration)
    The switch case in CallToolRequestSchema handler that dispatches execution to the tool's handler function.
    case 'get_regulatory_info':
      return await this.handleGetRegulatoryInfo(args);
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 for behavioral disclosure. It mentions 'Get' implying a read operation, but doesn't specify permissions, rate limits, data formats, or whether it's a real-time query versus cached data. For a tool with no annotations, this leaves significant gaps in understanding its behavior.

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 directly states the tool's purpose without fluff. It's appropriately sized and front-loaded, making it easy for an agent to parse quickly.

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 complexity (regulatory info from multiple agencies), lack of annotations, and no output schema, the description is insufficient. It doesn't explain what 'regulatory information' entails (e.g., approvals, bans, guidelines), return formats, or error handling, leaving the agent with incomplete context for effective 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?

The description adds no parameter-specific information beyond what's in the schema, which has 100% coverage (fully describes 'cid' as PubChem Compound ID). Since the schema does the heavy lifting, the baseline score of 3 is appropriate, as the description doesn't compensate but also doesn't detract.

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 from FDA, EPA, and international agencies'), making the purpose understandable. However, it doesn't explicitly differentiate from sibling tools like 'get_safety_data' or 'get_toxicity_info', which might overlap in regulatory contexts, preventing a perfect score.

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. With many sibling tools (e.g., 'get_safety_data', 'get_toxicity_info', 'assess_environmental_fate') that could relate to regulatory aspects, there's no indication of specific use cases, prerequisites, or exclusions, leaving the agent to guess.

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

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

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