Skip to main content
Glama

antibody_canonical_classes

Read-only

Assign each CDR of an antibody heavy, kappa or lambda variable domain to its canonical structure class: SCALOP's length-independent clusters of known loop conformations (CDR-H1, H2, L1, L2, L3; H3 has no canonical classes).

Input 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.
schemeNothe numbering the clusters are read in. Values: imgt (IMGT), chothia (Chothia).imgt
proteinYesthe protein sequence (one-letter amino acids); every heavy, kappa and lambda variable domain in it is classified.
speciesNospecies whose HMMs are preferred when numbering (ANARCI's default: human and mouse).
_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.
definitionNowhere each CDR begins and ends, by SCALOP's own tables. Values: imgt (IMGT), chothia (Chothia), north (North).north

Output Schema

NameRequiredDescriptionDefault
classesYesone `CDR: class` string per CDR, in sequence order (`H1: H1-13-A`, `None` where no class fits)
domainsYesper heavy, kappa or lambda domain: chain type, span, and per CDR the loop sequence, its class (cluster id), the median structure, the cluster's size, the outcome, SCALOP's threshold, every candidate cluster's score, and each residue's position, 0-based sequence index and log-odds in the assigned cluster

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior4/5

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

The annotations already establish a safe, read-only, closed-world operation. Beyond that, the description adds useful behavioral scope: it identifies which CDRs are classified and explicitly notes that H3 has no canonical classes.

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?

The definition is a single front-loaded sentence with no wasted preamble. The parenthetical CDR list and H3 exception are compact and relevant.

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?

Given the rich input schema, output schema, and annotations, the description covers the core classification behavior and the important H3 exclusion. It is nearly complete, though it omits any usage context for when this classification is appropriate relative to related antibody tools.

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 documents all six parameters, including the scheme, definition, species, and record inputs. The description reinforces which CDRs are classified but does not add parameter-level meaning beyond the schema.

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?

The description states a specific verb and resource: assign each antibody CDR to its canonical structure class. It also defines the resource as SCALOP's length-independent clusters and lists the relevant CDRs, though it does not explicitly differentiate the tool from nearby antibody-numbering or comparison siblings.

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

Usage Guidelines2/5

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

The description gives no explicit when-to-use guidance, no prerequisites, and no alternatives such as number_antibody or antibody_liabilities. Usage is only implied by the statement of purpose.

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