Skip to main content
Glama
Augmented-Nature

SureChEMBL MCP Server

get_chemical_properties

Retrieve molecular properties and descriptors for chemicals using SureChEMBL IDs to analyze patent-related chemical data.

Instructions

Get molecular properties and descriptors for a chemical by ID

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
chemical_idYesSureChEMBL chemical ID

Implementation Reference

  • The handler function that validates input, fetches chemical data from SureChEMBL API using the chemical_id, extracts and formats various molecular properties (e.g., SMILES, molecular weight, InChI, frequency), and returns a JSON response.
    private async handleGetChemicalProperties(args: any) {
      if (!args || typeof args.chemical_id !== 'string') {
        throw new McpError(ErrorCode.InvalidParams, 'Invalid chemical ID');
      }
    
      try {
        const response = await this.apiClient.get(`/chemical/id/${args.chemical_id}`);
    
        // Extract and format properties
        const chemical = response.data.data?.[0];
        if (!chemical) {
          throw new Error('Chemical not found');
        }
    
        const properties = {
          chemical_id: chemical.chemical_id,
          name: chemical.name,
          molecular_weight: chemical.mol_weight,
          smiles: chemical.smiles,
          inchi: chemical.inchi,
          inchi_key: chemical.inchi_key,
          is_element: chemical.is_element === '1',
          global_frequency: chemical.global_frequency,
          structural_alerts: chemical.mchem_struct_alert === '1',
          // Additional computed properties if available
          log_p: chemical.log_p,
          donor_count: chemical.donor_count,
          acceptor_count: chemical.accept_count,
          ring_count: chemical.ring_count,
          rotatable_bonds: chemical.rotatable_bond_count
        };
    
        return {
          content: [
            {
              type: 'text',
              text: JSON.stringify({
                chemical_id: args.chemical_id,
                properties: properties
              }, null, 2),
            },
          ],
        };
      } catch (error) {
        throw new McpError(
          ErrorCode.InternalError,
          `Failed to get chemical properties: ${error instanceof Error ? error.message : 'Unknown error'}`
        );
      }
    }
  • Input schema definition specifying that 'chemical_id' (string, SureChEMBL chemical ID) is required.
    inputSchema: {
      type: 'object',
      properties: {
        chemical_id: { type: 'string', description: 'SureChEMBL chemical ID' },
      },
      required: ['chemical_id'],
    },
  • src/index.ts:448-458 (registration)
    Tool registration in the MCP server's tools list, including name, description, and input schema.
    {
      name: 'get_chemical_properties',
      description: 'Get molecular properties and descriptors for a chemical by ID',
      inputSchema: {
        type: 'object',
        properties: {
          chemical_id: { type: 'string', description: 'SureChEMBL chemical ID' },
        },
        required: ['chemical_id'],
      },
    },
  • src/index.ts:564-565 (registration)
    Dispatch case in the MCP request handler switch statement that routes 'get_chemical_properties' calls to the handler method.
    case 'get_chemical_properties':
      return await this.handleGetChemicalProperties(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 states the action but does not reveal any behavioral traits like whether it's read-only, has rate limits, requires authentication, or what the output format might be. This leaves significant gaps in understanding how the tool behaves in practice.

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, clear sentence that directly states the tool's purpose without any unnecessary words or fluff. It is front-loaded and efficiently communicates the core function, making it highly concise 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 lack of annotations and output schema, the description is incomplete. It does not address behavioral aspects, usage context, or output details, which are crucial for a tool that likely returns complex data like molecular properties. This makes it inadequate for full understanding in a real-world scenario.

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 'chemical_id' documented as 'SureChEMBL chemical ID'. The description does not add any additional meaning or context beyond what the schema provides, such as examples or format details, so it meets the baseline score for high schema coverage.

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 'molecular properties and descriptors for a chemical by ID', making the purpose specific and understandable. However, it does not explicitly distinguish this tool from sibling tools like 'get_chemical_by_id' or 'get_chemical_frequency', which may have overlapping or similar purposes, so it falls short of 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, such as 'get_chemical_by_id' or 'search_chemicals_by_name'. It lacks context on prerequisites, exclusions, or specific scenarios where this tool is preferred, offering only a basic statement of function without usage instructions.

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

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