Skip to main content
Glama
Sign In
digeguigui

digeguigui

by Gaoshan0971
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

genetics_calculator

Calculate offspring genotype probabilities by entering parent genotypes for reptiles. Supports dominant, recessive, co-dominant, and polygenic inheritance.

Instructions

🧬 Punnett基因计算器 — 输入亲本基因型，输出子代概率表。支持显/隐/共显/多基因

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": {
      "parent1": "<parent1>",
      "parent2": "<parent2>"
    },
    "name": "genetics_calculator"
  }
}

Input Schema

NameRequiredDescriptionDefault
parent1Yes亲本1基因型，如 "het amel anery" 或 "pastel mojave"
parent2Yes亲本2基因型
speciesNo物种名(可选)，用于加载物种基因库。默认: 玉米蛇

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.3/5.0
Behavior4/5

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

No annotations, but description clarifies it's a read-only calculator producing a table. Does not mention limitations, error handling, or data persistence. Supported inheritance types are disclosed, adding value.

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?

Single sentence with emoji, efficiently communicates purpose and supported features. No wasted words.

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?

No output schema, so description should detail return structure. Only says 'probability table', lacking format or explanation. Missing edge cases, species database behavior, and error handling. Adequate but not fully informative.

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 has 100% coverage with clear descriptions for each parameter. Description adds context on supported inheritance types and mentions optional species for gene database loading, beyond schema.

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?

Description explicitly states function: input parental genotypes, output offspring probability table. Lists supported inheritance types (dominant/recessive/codominant/multiple genes). No sibling genetics tools exist, so no confusion.

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?

Implies use for genetic cross calculation, but lacks explicit guidance on when to use or prerequisites (e.g., valid gene names, format). Since no alternative genetics tools exist, the impact is minor.

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