Skip to main content
Glama

Sgd

by io.github.pipeworx-io

Get Gene Go

get_gene_go
Read-onlyIdempotent

Get Gene Ontology (GO) annotations for a yeast (S. cerevisiae) gene/locus from SGD (Saccharomyces Genome Database). Accepts a systematic name (e.g. YAL001C), a standard gene name (e.g. TFC3), or an SGDID (e.g. S000000001). Returns GO terms with their GO id, aspect (molecular function / biological process / cellular component), and supporting evidence. Keyless.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesSystematic name (YAL001C), gene name (TFC3), or SGDID (S000000001).

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already cover read-only, open-world, idempotent, non-destructive behavior. The description adds that it returns GO terms with aspect and evidence, which is useful context beyond annotations.

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 two sentences covering purpose, input, and output without unnecessary words. Every sentence adds value.

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

Completeness5/5

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

Given no output schema, the description explains the return format (GO id, aspect, evidence). The parameter is well-documented. Adequate for a straightforward retrieval tool.

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?

Schema coverage is 100%, and the description adds examples of acceptable ID formats (systematic name, gene name, SGDID), enhancing the schema description which already lists them.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states it retrieves Gene Ontology annotations for yeast genes from SGD, specifying the species, database, and return type. This distinguishes it from siblings like 'get_gene' (general info) and 'search_genes'.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description mentions 'Keyless' and accepts multiple ID formats, providing clear input guidelines. It does not explicitly contrast with alternatives but implies usage for GO annotations specifically.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Sgd toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.6/5.0
Disambiguation2/5

Several tools have heavily overlapping purposes: ask_pipeworx, ask_pipeworx_beta (explicitly identical today), ask_pipeworx_grounded, deep_research, and validate_claim all route factual questions through similar pipelines. The polymarket_* cluster also blurs together, with arbitrage, edges, fill_risk, kalshi_spread, and bet_research all analyzing prediction-market mispricings from different angles.

Naming Consistency3/5

All names use consistent snake_case, but the verb/noun pattern is mixed: some are verb-first (compare_entities, generate_llms_txt, validate_claim), others noun-first (polymarket_edges, entity_profile, ai_visibility_check), and some are bare product names (ask_pipeworx, pipeworx_trending). Readable overall, but no single predictable convention.

Tool Count2/5

34 tools is far too many for a coherent server, especially since the server is named 'Sgd' but only 3 tools relate to yeast genetics. The remaining 31 tools span data lookup, prediction markets, memory, subscriptions, npm scanning, and llms.txt generation—an unfocused grab bag that should be split into multiple servers.

Completeness2/5

As an SGD yeast-genome server, the surface is thin: search, get_gene, and get_gene_go cover basic lookup but miss sequences, interactions, strains, homologs, and other standard SGD data. As a general data utility, the collection is broad but incoherent, with several one-off tools (generate_llms_txt, scan_dependency) that have no connection to the rest.

Resources