Skip to main content
Glama

build_codon_table_from_cds

Read-only

Build a codon-usage table from a genome's CDS FASTA (an NCBI cds_from_genomic.fna): either from its highly-expressed genes — the ribosomal proteins, which is what a codon-optimisation reference table means — or from every CDS in the genome.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "build_codon_table_from_cds"
  }
}

Input Schema

NameRequiredDescriptionDefault
fileNothe CDS FASTA to read, by name, from the project or the `_files` sent with the call. Empty reads the only FASTA there.
modeNo`heg` builds the table from the ribosomal-protein genes, which is the reference set a codon-optimisation table means. `genome` uses every CDS, which is the honest choice for a plasmid or any corpus whose highly-expressed genes are not in it. Values: heg (Highly-expressed genes (ribosomal proteins)), genome (Every CDS in the corpus).heg
fastaNoor the CDS FASTA itself, in frame, one record per CDS.
_filesNoThe project: record references shaped like _subject. Their records become library documents a tool names in sequences/parts/document; a trace or alignment is found by file name.
_subjectNoThe record to act on: exactly one of sequence, accession (+source), sample (an id from list_samples) or file ({name, text} or {name, base64}); record_index picks one record of several.

Output Schema

NameRequiredDescriptionDefault
gc3YesGC at the third codon position of the reference set, the usual summary of a genome’s codon bias
tsvYesthe usage table as a Kazusa-style TSV — wire it into optimize_sequence, codon_usage_analysis or design_expression_variants
modeYeswhich reference set this table was built from
codonsYescodons counted
cdsUsedYesCDS records that went into the table
cdsTotalYesCDS records read from the corpus
backfilledYesamino acids absent from the highly-expressed set, taken from the whole genome instead. Empty in genome mode

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered without description help. The description adds useful domain context (that HEG means ribosomal proteins) but says nothing about failure modes, what happens when the input has no ribosomal-protein annotations, or scale limits on genome-wide builds. Adequate but not rich.

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?

A single front-loaded sentence with no filler, and the input format appears early where it is most useful. The em-dash nesting of the HEG gloss makes it slightly harder to parse than a two-sentence split would be.

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

Completeness4/5

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

With an output schema present and full schema coverage, the description does not need to explain return values, and annotations cover safety. It is nearly complete for a moderately complex, nested-parameter tool, missing only fallback behavior when a corpus lacks the highly-expressed gene set.

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% and both `mode` values are already spelled out in the schema with the same ribosomal-protein gloss, so the description adds little new parameter meaning. Baseline 3 applies when the schema does the heavy lifting; the mode rationale in the description only marginally extends it.

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?

Specific verb+resource: 'Build a codon-usage table from a genome's CDS FASTA', with the accepted input format (NCBI `cds_from_genomic.fna`) named. The two operating modes are stated up front. It does not differentiate itself from a sibling like codon_table_fetch, which is a plausible confusion (fetch a prebuilt table vs. derive one from your own CDS), so it stops short of a 5.

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?

Offers genuine selection guidance between the two modes: `heg` is 'what a codon-optimisation reference table means', while `genome` is 'the honest choice for a plasmid or any corpus whose highly-expressed genes are not in it' — a clear condition-based rule. It gives no guidance on when to use this tool versus fetching a standard table or running codon_usage_analysis.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources