Skip to main content
Glama

convert_biotech

Converts bioinformatics files such as FASTA, FASTQ, VCF, GFF/GTF, and PDB into JSON, CSV, or FASTA for local analysis and data exchange.

Instructions

Convert bioinformatics files: FASTA↔JSON/CSV, FASTQ→JSON/FASTA, VCF→JSON/CSV, GFF/GTF→JSON/CSV, PDB→JSON

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "inputPath": "<inputPath>",
      "outputPath": "<outputPath>"
    },
    "name": "convert_biotech"
  }
}

Input Schema

NameRequiredDescriptionDefault
inputPathYesAbsolute path to input biotech file
outputPathYesAbsolute path for output file (include extension)
inputFormatNoInput format (auto-detected if not provided)
outputFormatNoOutput format

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.1.0

TDQS

A3.7/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden and falls well short: it does not say whether an existing outputPath is overwritten, whether conversion is lossy (FASTQ→FASTA drops quality scores), what happens on unsupported pairs or malformed input, or whether large files are size-limited. Only the directional matrix hints at behavior.

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?

A single sentence that front-loads the verb and packs the entire supported-conversion matrix into compact arrow notation with no filler. Every token carries information an agent needs.

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?

For a 4-parameter file-writing tool with no annotations and no output schema, the description covers what it converts but omits the operational details that matter most: overwrite semantics, lossy conversions, and error behavior. It is adequate to select the tool but thin for invoking it safely.

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%, so the baseline is 3, but the description adds genuine meaning beyond the enums by specifying which input/outputFormat combinations are valid and directional (e.g. FASTQ converts to JSON/FASTA but not the reverse), which the schema alone cannot express. It still says nothing about auto-detection behavior when inputFormat is omitted, which the schema mentions.

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?

States a specific verb (convert) and resource (bioinformatics files) and then enumerates the exact supported format pairs with directionality (FASTA↔JSON/CSV, FASTQ→JSON/FASTA, VCF→JSON/CSV, GFF/GTF→JSON/CSV, PDB→JSON). The domain qualifier 'bioinformatics' cleanly separates it from domain siblings like convert_3d, convert_chemistry, or convert_astronomy.

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

Usage Guidelines3/5

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

The conversion matrix implicitly tells the agent which format pairs are legal, which is real usage guidance, but there is no explicit when-to-use versus batch_convert (multi-file) or get_supported_formats, and no statement of prerequisites or exclusions. Usage must be inferred from the arrow notation rather than stated.

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