Skip to main content
Glama
WormBase

WormBase MCP Server

Official
by WormBase

get_paper

Retrieve scientific paper details including authors, abstract, and associated genes using WormBase or PubMed identifiers.

Instructions

Get information about a scientific paper/publication including authors, abstract, and associated genes.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesPaper identifier - WormBase paper ID (e.g., 'WBPaper00000001') or PubMed ID

Implementation Reference

  • The handler function for the 'get_paper' tool. It invokes WormBaseClient.getEntity with type 'paper' and specific widgets ['overview', 'referenced_genes'], formats the result as JSON text, and handles errors.
    async ({ id }) => {
      try {
        const data = await client.getEntity("paper", id, ["overview", "referenced_genes"]);
        return {
          content: [{ type: "text", text: JSON.stringify(data, null, 2) }],
        };
      } catch (error) {
        return {
          content: [{ type: "text", text: `Error fetching paper: ${error}` }],
          isError: true,
        };
      }
    }
  • Zod schema defining the input parameters for the 'get_paper' tool: a required string 'id' for the paper identifier.
    {
      id: z.string().describe("Paper identifier - WormBase paper ID (e.g., 'WBPaper00000001') or PubMed ID"),
    },
  • src/index.ts:270-289 (registration)
    MCP tool registration for 'get_paper' using McpServer.tool(), specifying name, description, input schema, and handler.
    server.tool(
      "get_paper",
      "Get information about a scientific paper/publication including authors, abstract, and associated genes.",
      {
        id: z.string().describe("Paper identifier - WormBase paper ID (e.g., 'WBPaper00000001') or PubMed ID"),
      },
      async ({ id }) => {
        try {
          const data = await client.getEntity("paper", id, ["overview", "referenced_genes"]);
          return {
            content: [{ type: "text", text: JSON.stringify(data, null, 2) }],
          };
        } catch (error) {
          return {
            content: [{ type: "text", text: `Error fetching paper: ${error}` }],
            isError: true,
          };
        }
      }
    );
  • WormBaseClient.getEntity method: generic implementation to fetch data for any WormBase entity type (including 'paper') by querying REST API widgets and cleaning the response.
    async getEntity(
      type: EntityType,
      id: string,
      widgets?: string[]
    ): Promise<Record<string, unknown>> {
      const defaultWidgets = ["overview"];
      const requestedWidgets = widgets || defaultWidgets;
    
      const result: Record<string, unknown> = { id, type };
    
      for (const widget of requestedWidgets) {
        try {
          const url = `${this.baseUrl}/rest/widget/${type}/${encodeURIComponent(id)}/${widget}`;
          const data = await this.fetch<any>(url);
          result[widget] = this.cleanWidgetData(data);
        } catch (error) {
          result[widget] = { error: `Failed to fetch ${widget}` };
        }
      }
    
      return result;
    }
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 tool retrieves information but lacks details on permissions, rate limits, error handling, or response format. 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.

Conciseness4/5

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

The description is a single, efficient sentence that front-loads the purpose. It avoids redundancy and wastes no words, though it could be slightly more structured for clarity.

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 simplicity (1 parameter, no output schema, no annotations), the description is minimally adequate. It covers the basic purpose but lacks behavioral context and usage guidelines, making it incomplete for optimal agent operation.

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?

Schema description coverage is 100%, so the schema already documents the 'id' parameter. The description does not add any parameter-specific details beyond what the schema provides, such as examples or constraints. Baseline 3 is appropriate when the schema handles parameter documentation.

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 resource ('scientific paper/publication') along with specific information returned ('authors, abstract, and associated genes'). It distinguishes this from sibling tools like 'get_gene' or 'get_disease' by focusing on papers, though it doesn't explicitly contrast them.

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 like 'search' or other 'get_' tools. The description implies usage for retrieving paper details but offers no context about prerequisites, exclusions, or comparative scenarios.

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