Wegene Assistant MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| WEGENE_API_KEY | Yes | Your WeGene Open API key | |
| WEGENE_API_SECRET | Yes | Your WeGene Open API secret |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| wegene-oauthB | Authorizing a user's account using WeGene Open API with oAuth2 protocol and retrieve a valid access token for further use |
| wegene-get-profilesB | Retrieve all the profiles under the current account |
| wegene-get-report-infoB | Get all available report information |
| wegene-get-reportC | Get a specific genetic test report from a profile |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 4 tools
Each tool has a clearly distinct purpose: get-profiles retrieves account profiles, get-report fetches a specific genetic report, get-report-info lists available reports, and oauth handles authentication. There is no overlap in functionality, making tool selection unambiguous.
All tools follow a consistent 'wegene-verb-noun' pattern with hyphens, using clear verbs like 'get' and 'oauth'. This uniformity makes the tool set predictable and easy to understand.
Four tools are reasonable for a genetic data server, covering authentication, profile retrieval, and report access. It might benefit from additional operations like updating profiles or deleting data, but the core scope is well-defined.
The tools cover authentication and read operations (profiles and reports) adequately, but there are notable gaps in write operations such as creating, updating, or deleting profiles or reports. This limits the server to read-only workflows.