Skip to main content
Glama
xraywu

Wegene Assistant MCP Server

by xraywu

wegene-get-report-info

Retrieve comprehensive genetic report data from WeGene to analyze health insights and ancestry information through API integration.

Instructions

Get all available report information

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The specific handler branch in handle_call_tool() that executes the 'wegene-get-report-info' tool by calling get_report_info() and wrapping the result in TextContent.
    elif name == "wegene-get-report-info":
        return [
            types.TextContent(
                type="text",
                text=get_report_info()
            )
        ]
  • Core implementation logic of the tool: loads the static reports configuration from config/reports.json and returns it as a JSON string.
    def get_report_info() -> str:
        """
        Retrieve all report info. Since WeGene does not have a report list API, prebuild with config file.
        :return: JSON string of all reports
        """
        # Read config file
        reports_path = "config/reports.json"
        with open(reports_path, "r", encoding="utf-8") as f:
            reports = json.load(f)
        return json.dumps(reports, ensure_ascii=False)
  • Registration of the 'wegene-get-report-info' tool in the list_tools() function, including name, description, and schema.
    types.Tool(
        name="wegene-get-report-info",
        description="Get all available report information",
        inputSchema={
            "type": "object",
            "properties": {}
        },
    ),
  • Input schema for the tool: an object with no properties (no input parameters required).
        "type": "object",
        "properties": {}
    },
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. It states this is a 'Get' operation, implying read-only behavior, but doesn't specify authentication needs, rate limits, error conditions, or what 'all available report information' entails (e.g., format, scope, or limitations). This leaves significant gaps 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 directly states the tool's purpose without any fluff or redundancy. It's appropriately sized for a zero-parameter tool and front-loads the essential information clearly.

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 doesn't explain what 'report information' includes, how it's structured, or any behavioral aspects like authentication or errors. For a tool that likely returns data, more context is needed to guide the agent effectively.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool has zero parameters, and schema description coverage is 100%, so there's no need for parameter documentation in the description. The description appropriately doesn't discuss parameters, aligning with the schema's empty properties. A baseline of 4 is given since no parameters exist, and the description doesn't add unnecessary details.

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 action ('Get') and resource ('all available report information'), making the purpose understandable. However, it doesn't differentiate this tool from its sibling 'wegene-get-report', leaving some ambiguity about what distinguishes 'report information' from just 'report'.

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 'wegene-get-report' or 'wegene-get-profiles'. There's no mention of prerequisites, context, or exclusions, leaving the agent with no usage direction beyond the basic purpose.

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/xraywu/mcp-wegene-assistant'

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