Skip to main content
Glama

get_toxicity_info

Retrieve toxicity data for chemical compounds, including LD50 values, carcinogenicity, and mutagenicity information from PubChem's database.

Instructions

Get toxicity data including LD50, carcinogenicity, and mutagenicity

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
cidYesPubChem Compound ID (CID)

Implementation Reference

  • The main handler function for the 'get_toxicity_info' tool. It currently returns a placeholder response indicating that toxicity information retrieval is not yet implemented.
    private async handleGetToxicityInfo(args: any) {
      return { content: [{ type: 'text', text: JSON.stringify({ message: 'Toxicity info not yet implemented', args }, null, 2) }] };
    }
  • Schema definition for the 'get_toxicity_info' tool, specifying the input parameters (requires 'cid') and description.
    {
      name: 'get_toxicity_info',
      description: 'Get toxicity data including LD50, carcinogenicity, and mutagenicity',
      inputSchema: {
        type: 'object',
        properties: {
          cid: { type: ['number', 'string'], description: 'PubChem Compound ID (CID)' },
        },
        required: ['cid'],
      },
    },
  • src/index.ts:794-795 (registration)
    Tool registration in the main request handler switch statement, dispatching to the specific handler method.
    case 'get_toxicity_info':
      return await this.handleGetToxicityInfo(args);
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions the types of toxicity data retrieved but doesn't cover aspects like data sources, accuracy, rate limits, authentication needs, or what happens if the CID is invalid. For a tool with no annotation coverage, this leaves significant gaps in understanding its operational 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 that directly states the tool's purpose without unnecessary words. It's front-loaded with the core action and includes specific data types, making it easy to parse quickly. Every part of the sentence contributes meaningfully.

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 toxicity data retrieval, no annotations, and no output schema, the description is incomplete. It doesn't explain the return format, data units, potential errors, or how to interpret results like LD50 values. For a tool with rich data output and no structured support, more contextual information is needed to guide 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 input schema has 100% description coverage, with the 'cid' parameter clearly documented as 'PubChem Compound ID (CID)'. The description adds no additional parameter information beyond what's in the schema, such as format examples or constraints. Baseline 3 is appropriate since the schema does the heavy lifting, but the description doesn't enhance parameter understanding.

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 'toxicity data', specifying the types of data included (LD50, carcinogenicity, mutagenicity). It distinguishes from siblings like 'get_safety_data' or 'get_regulatory_info' by focusing specifically on toxicity metrics. However, it doesn't explicitly contrast with these similar tools, keeping it at a 4 rather than a 5.

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 like 'get_safety_data' or 'get_regulatory_info', which might overlap in scope. There's no mention of prerequisites, limitations, or specific contexts where this tool is preferred. It simply states what it does without usage context.

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