Skip to main content
Glama
WormBase

WormBase MCP Server

Official
by WormBase

get_expression

Retrieve gene expression patterns including tissue/cell localization, life stage timing, and associated images from the WormBase database for C. elegans research.

Instructions

Get expression pattern information for a gene including tissue/cell expression, life stage expression, and expression images.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesGene identifier

Implementation Reference

  • The main handler function that fetches gene expression data from the WormBase API endpoint and processes it using the cleanWidgetData helper.
    async getExpression(id: string): Promise<Record<string, unknown>> {
      const url = `${this.baseUrl}/rest/widget/gene/${encodeURIComponent(id)}/expression`;
      const data = await this.fetch<any>(url);
      return this.cleanWidgetData(data);
    }
  • src/index.ts:202-221 (registration)
    MCP server tool registration for 'get_expression', including name, description, input schema, and handler that calls the client method.
    server.tool(
      "get_expression",
      "Get expression pattern information for a gene including tissue/cell expression, life stage expression, and expression images.",
      {
        id: z.string().describe("Gene identifier"),
      },
      async ({ id }) => {
        try {
          const data = await client.getExpression(id);
          return {
            content: [{ type: "text", text: JSON.stringify(data, null, 2) }],
          };
        } catch (error) {
          return {
            content: [{ type: "text", text: `Error fetching expression: ${error}` }],
            isError: true,
          };
        }
      }
    );
  • Zod input schema for the get_expression tool, requiring a gene 'id' parameter.
    {
      id: z.string().describe("Gene identifier"),
    },
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 information, implying a read-only operation, but doesn't clarify aspects like authentication requirements, rate limits, error handling, or response format. For a tool with no annotation coverage, this leaves significant behavioral gaps.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, well-structured sentence that efficiently conveys the tool's purpose and scope. It's front-loaded with the main action and includes specific details without unnecessary elaboration. However, it could be slightly more concise by avoiding the list format, but overall it's effective and wastes no words.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's complexity (simple read operation with one parameter), lack of annotations, and no output schema, the description is minimally adequate. It covers what information is retrieved but omits behavioral details and usage context. For a tool with no structured output or safety hints, it should provide more completeness, such as response format or error cases.

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 'id' parameter documented as 'Gene identifier'. The description doesn't add any parameter-specific information beyond what the schema provides, such as examples or constraints. Given the high schema coverage, a baseline score of 3 is appropriate, as the schema handles the parameter documentation 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 tool's purpose: 'Get expression pattern information for a gene' with specific details about what information is retrieved (tissue/cell expression, life stage expression, expression images). It uses a specific verb ('Get') and resource ('expression pattern information for a gene'), making the purpose unambiguous. However, it doesn't explicitly differentiate from sibling tools like 'get_gene', which might retrieve different gene information.

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 sibling tools like 'get_gene' or 'search', nor does it specify prerequisites or contexts for usage. The agent must infer usage based on the purpose alone, which is insufficient for optimal tool selection.

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/WormBase/wormbase-mcp'

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