Skip to main content
Glama

get_regulatory_info

Retrieve regulatory information 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 primary handler function executing the 'get_regulatory_info' tool logic. It currently returns a placeholder response 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) }] };
    }
  • Input schema definition for the 'get_regulatory_info' tool, specifying required 'cid' parameter.
    inputSchema: {
      type: 'object',
      properties: {
        cid: { type: ['number', 'string'], description: 'PubChem Compound ID (CID)' },
      },
      required: ['cid'],
    },
  • src/index.ts:672-682 (registration)
    Tool registration in the ListTools response, defining 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)
    Dispatch routing in the CallToolRequestSchema handler that calls the specific tool handler.
    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 the full burden of behavioral disclosure. It mentions retrieving information but doesn't specify aspects like data sources, rate limits, authentication needs, or response format. For a tool with no annotation coverage, this is a significant gap in transparency.

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 directly states the tool's purpose without unnecessary words. It is appropriately sized and front-loaded, making it easy 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 of regulatory data and lack of annotations or output schema, the description is insufficient. It doesn't explain what 'regulatory information' entails (e.g., approvals, restrictions, guidelines), how results are structured, or any limitations, leaving key contextual gaps 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 the input schema provides. With 100% schema description coverage (the 'cid' parameter is documented as 'PubChem Compound ID'), the baseline score of 3 is appropriate, as the schema handles the parameter semantics adequately.

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?

No guidance is provided on when to use this tool versus alternatives. With siblings like 'get_safety_data' and 'get_toxicity_info' potentially covering similar regulatory aspects, the description lacks any indication of scope, prerequisites, or distinctions, leaving usage unclear.

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

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