Skip to main content
Glama

get_assay_info

Retrieve detailed bioassay data from PubChem by entering an Assay ID (AID) to access experimental protocols, results, and chemical activity information.

Instructions

Get detailed information for a specific bioassay by AID

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
aidYesPubChem Assay ID (AID)

Implementation Reference

  • The main handler function that implements the get_assay_info tool. It fetches detailed assay information from the PubChem API using the provided AID and returns the JSON response.
    private async handleGetAssayInfo(args: any) {
      try {
        const response = await this.apiClient.get(`/assay/aid/${args.aid}/JSON`);
        return {
          content: [
            {
              type: 'text',
              text: JSON.stringify(response.data, null, 2),
            },
          ],
        };
      } catch (error) {
        throw new McpError(
          ErrorCode.InternalError,
          `Failed to get assay info: ${error instanceof Error ? error.message : 'Unknown error'}`
        );
      }
    }
  • The input schema definition for the get_assay_info tool, specifying that it requires a numeric 'aid' parameter (PubChem Assay ID).
    name: 'get_assay_info',
    description: 'Get detailed information for a specific bioassay by AID',
    inputSchema: {
      type: 'object',
      properties: {
        aid: { type: 'number', description: 'PubChem Assay ID (AID)' },
      },
      required: ['aid'],
    },
  • src/index.ts:782-783 (registration)
    The switch case in the tool request handler that routes calls to 'get_assay_info' to the handleGetAssayInfo method.
    case 'get_assay_info':
      return await this.handleGetAssayInfo(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 states the tool retrieves 'detailed information' but doesn't specify what that includes (e.g., assay type, results, metadata), whether it's a read-only operation, potential rate limits, or error handling. 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 that front-loads the core purpose ('Get detailed information for a specific bioassay') and includes the key identifier. There is no wasted wording, 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 complexity of bioassay data and the lack of annotations and output schema, the description is incomplete. It doesn't explain what 'detailed information' entails, potential response formats, or how this tool fits into the broader context of sibling tools (e.g., vs. 'search_bioassays'), 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?

The input schema has 100% description coverage, with the 'aid' parameter clearly documented as 'PubChem Assay ID (AID)'. The description adds minimal value beyond this, only reiterating the parameter in 'by AID' without providing additional context like format examples or constraints. This meets the baseline 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 tool's purpose with a specific verb ('Get') and resource ('detailed information for a specific bioassay'), and it identifies the key identifier ('by AID'). However, it doesn't explicitly differentiate this tool from its sibling 'search_bioassays', which might also retrieve bioassay information but through search rather than direct lookup.

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. It doesn't mention prerequisites (e.g., needing a specific AID), exclusions, or how it differs from sibling tools like 'search_bioassays' or 'get_compound_bioactivities', leaving the agent to infer 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