Skip to main content
Glama
Sign In
seosiri-biorobotics

seosiri-biorobotics

Official
by SEOSiri-Official
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

calculate_dna_melting_temp

Calculate GC-content and melting temperature of a DNA sequence to set the heating plate temperature for physical deck operations.

Instructions

Calculates the GC-content and melting temperature (Tm) of a DNA sequence to determine the required heating plate temperature on the physical deck.

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": {
      "dna_sequence": "<dna_sequence>"
    },
    "name": "calculate_dna_melting_temp"
  }
}

Input Schema

NameRequiredDescriptionDefault
dna_sequenceYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.2

TDQS

B3.3/5.0
Behavior2/5

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

No annotations exist, so description carries full burden. It mentions outputs but does not disclose behavioral traits like formula assumptions, input validation, error handling, or limits on sequence length/composition.

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?

Single sentence efficiently communicates purpose and practical outcome. No wasted words, but could be slightly expanded for key details.

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 simple one-parameter tool with output schema, the description is adequate but could mention typical formula used (e.g., nearest-neighbor) or salt dependency to be fully informative.

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

Parameters2/5

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

Only one parameter, dna_sequence, with 0% schema description coverage. The description simply says 'DNA sequence' without adding format, allowed characters, case sensitivity, or length constraints beyond the parameter name.

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?

Clearly states it calculates GC-content and melting temperature from a DNA sequence, and explicitly links to determining heating plate temperature. Distinguishes from sibling tools which focus on pipetting, genomic data fetching, plate coordinates, and spatial intent.

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?

Implies usage for DNA melting temperature calculation, but does not provide explicit guidance on when to use versus alternatives, nor any exclusions or prerequisites.

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

Deploy Server

Other Tools