Skip to main content
Glama

jean — Molecular Biology & Genomics

antibody_isotype

Read-only

Name the CONSTANT region of an antibody chain: which immunoglobulin gene and allele it carries (IGHG1, IGHA2, IGKC, IGLC2 …), and where each IMGT domain sits on it — CH1, the hinge, CH2, CH3, the secretory tail and the membrane exons, or the single C region of a light chain. A domain search says 'a C1-set immunoglobulin domain'; this says which isotype it is. Reads IMGT/GENE-DB's own per-label translations for every species, and is graded against UniProtKB's curated human constant chains and their CH1/hinge/CH2/CH3 regions.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
_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.
proteinYesthe chain (one-letter amino acids); the constant region in it is found, so a whole heavy chain is fine.
speciesNoonly consider genes of this species, spelled as IMGT spells it (Homo sapiens, Mus musculus). Left out, every species in the catalogue competes and the answer says which won.
_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.
minIdentityNoa domain matching less of its reference than this is not reported.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
geneYesthe IMGT gene the constant region matches (IGHG1)
alleleYesthe allele, as IMGT numbers them (01)
domainsYeseach IMGT label placed on the chain: label, start, end (1-based inclusive), identity, coverage
speciesYesthe species whose gene answered
identityYesidentical residues over every aligned column, 0 to 1

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

With readOnly/openWorld/destructive annotations already covering safety, the description adds valuable provenance: it reads IMGT/GENE-DB per-label translations for every species and is graded against UniProtKB curated human constant chains. It does not discuss error modes or rate limits, but adds meaningful 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.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the core purpose and well-organized into purpose, contrast, and provenance sentences. Slight redundancy repeats CH1/hinge/CH2/CH3 and the domain list, but overall efficient for the tool's complexity.

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 the output schema, annotations, and full schema coverage, the description supplies what is missing: clear purpose, contrast with domain search, and data-source behavior. Nothing essential for an agent to invoke it correctly is absent.

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%, so the schema already defines protein, species, minIdentity, and record parameters. The description adds no parameter-level detail beyond what the schema provides, making the baseline 3 appropriate.

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 states a specific verb and resource: name the constant region of an antibody chain, identifying immunoglobulin gene/allele and IMGT domain positions. It explicitly distinguishes itself from a generic domain search, so an agent can tell it apart from scan_protein_domains-style siblings.

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?

Contrasts with domain search by explaining that this tool reports the isotype, not just a C1-set domain. Provides clear context for use, but does not name specific sibling tools or state when not to use it.

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