Skip to main content
Glama

jean — Molecular Biology & Genomics

protein_digest

Read-only

In-silico proteolytic digest of a protein (ExPASy PeptideCutter / PeptideMass): peptides with coordinates, average and monoisotopic masses, m/z per charge state, and the MS mass-window filter. 49 proteases and chemicals — or an enzyme of your own written in RPG rule grammar — one or several at a time; a multi-enzyme digest runs concurrently (all at once, products re-digested until nothing changes) or sequentially (one result per enzyme).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
modeNomulti-enzyme only. 'concurrent' = all at once, re-digesting products until nothing changes (can cut where no single enzyme cuts the intact chain); 'sequential' = one result per enzyme, each on the intact protein.concurrent
semiNoalso emit semi-enzymatic peptides (one ragged terminus).
_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.
enzymeNoprotease or chemical (single-enzyme digest), or 'custom' to use `customCleave`. Values: arg-c (Arg-C proteinase), asp-n (Asp-N endopeptidase), asp-n-sg (Asp-N, sequencing grade (D and C)), bnps-skatole (BNPS-Skatole), bromelain (Bromelain), caspase-1 (Caspase 1), caspase-10 (Caspase 10), caspase-2 (Caspase 2), caspase-3 (Caspase 3), caspase-4 (Caspase 4), caspase-5 (Caspase 5), caspase-6 (Caspase 6), caspase-7 (Caspase 7), caspase-8 (Caspase 8), caspase-9 (Caspase 9), chymotrypsin-high (Chymotrypsin (high specificity)), chymotrypsin-low (Chymotrypsin (low specificity)), clostripain (Clostripain (Arg-C)), cnbr (CNBr), elastase (Elastase), enterokinase (Enterokinase), factor-xa (Factor Xa), ficin (Ficin), formic-acid (Formic acid), glu-c (Glu-C (D and E)), glutamyl-endopeptidase (Glutamyl endopeptidase), granzyme-b (Granzyme B), hydroxylamine (Hydroxylamine), iodosobenzoic-acid (Iodosobenzoic acid), lysc (Lys-C), lysn (Lys-N), lysarginase (LysargiNase), neutrophil-elastase (Neutrophil elastase), ntcb (NTCB (2-nitro-5-thiocyanobenzoic acid)), papain (Papain), pepsin-ph2.0 (Pepsin (pH > 2)), pepsin-ph1.3 (Pepsin (pH 1.3)), proalanase (ProAlanase), proline-endopeptidase (Proline endopeptidase), proteinase-k (Proteinase K), staph-peptidase-i (Staphylococcal peptidase I), tev (TEV protease (Tobacco Etch Virus)), thermolysin (Thermolysin), thrombin (Thrombin), thrombin-sg (Thrombin (sequencing grade)), trypsin (Trypsin), trypsin-low (Trypsin (low specificity)), trypsin-simple (Trypsin (simple K/R)), alp (α-lytic protease (aLP)), custom (Custom cleavage rule).trypsin
chargesNocharge states to report m/z for, e.g. [1,2,3] — [M+zH]z+ from the monoisotopic mass.
enzymesNotwo or more proteases for a multi-enzyme digest; overrides `enzyme`. Order matters in concurrent mode. 'custom' takes its place in the order like any other.
massMaxNokeep only peptides at or below this monoisotopic mass [Da]; omit for no upper bound.
massMinNokeep only peptides at or above this monoisotopic mass [Da]; omit for no lower bound.
proteinYesthe protein sequence (unambiguous one-letter codes); wire it from translate_sequence.
_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.
cysteineNocysteine alkylation applied before the digest, as ExPASy PeptideMass offers it. Mass deltas are Unimod's.none
maxLengthNodrop peptides longer than this (residues).
minLengthNodrop peptides shorter than this (residues).
customRegexNothe 'custom' enzyme as a regular expression instead of RPG grammar (pyteomics' `rule=`): it matches at P1 and the cut falls after the match, e.g. '[KR]' cleaves after K or R. Single-enzyme only, and mutually exclusive with `customCleave`. Advanced.
customCleaveNocleaving rules for the 'custom' enzyme, in RPG grammar: the comma is the cut, so '(,A)' cleaves before A and '(K or R,)' after K or R. Empty parentheses mean any residue.
metOxidationNomethionine oxidation. 'all' oxidises every Met (masses move, peptide list unchanged); 'both' lists each Met peptide TWICE, unmodified and oxidised, as PeptideMass does.off
keilExceptionsNoapply Keil's exception rules (sites trypsin does NOT cut despite matching). Only defined for trypsin. PeptideCutter and Bioconductor cleaver apply these by default, which is why this does too; pyteomics does not, so turn it off to cross-check against pyteomics.
missedCleavagesNosingle enzyme: allow up to this many internal sites per peptide (pyteomics). Multi-enzyme: append runs of up to this many merged adjacent peptides (RPG).
customExceptionsNoexceptions for the 'custom' enzyme; each must repeat the rule it blocks, e.g. '(K or R,)(P)' = not when P follows.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
countYespeptides returned after any mass filter
sitesYescleavage-site positions (0-based residue index the next peptide starts at)
resultsYesmulti-enzyme only: one entry per digestion (per enzyme in sequential mode, one for the whole set in concurrent), each with its own peptides, sites and coverage
coverageYesfraction of the protein covered by the peptides returned
peptidesYespeptides with start/end, sequence, missed cleavages, masses and m/z (all results pooled in multi-enzyme mode)
totalPeptidesYespeptides the digest produced BEFORE the mass filter

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds genuine behavioral context beyond that: what the digest returns (peptides with coordinates and masses), and the semantics of concurrent (re-digest until stable, can cut where no single enzyme would) versus sequential (one result per enzyme) — the latter only partially mirrored in the schema. No contradictions.

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?

Two sentences, front-loaded with the core action and outputs before the enzyme-count and mode details. Dense but every phrase carries information; slightly packed with parenthetical tool names that stretch the opening clause.

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?

An output schema exists, so return values need not be spelled out (and the description still sketches them), and annotations cover the safety profile. For a 19-parameter tool with nested objects and 100% schema coverage, the description supplies enough orientation about scope, outputs, and enzyme/mode behavior; only explicit sibling routing is missing.

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 19 parameters thoroughly. The description adds gloss on the 49 proteases, custom RPG rule grammar, and the mass-window filter, but no syntax or format detail beyond what the schema provides; baseline 3 is 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?

States a specific verb and resource ('in-silico proteolytic digest of a protein') plus the concrete outputs (peptides with coordinates, average/monoisotopic masses, m/z per charge state, mass-window filter) and anchors to ExPASy PeptideCutter/PeptideMass. An agent can distinguish this from siblings like peptide_mass, digest_fragments or enzyme_cut_counts without opening the schema.

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 description explains how the multi-enzyme modes behave (concurrent vs sequential) which implicitly guides parameter choice, but never says when to reach for this tool versus peptide_mass, digest_fragments or enzyme_cut_counts. Usage is inferable from the stated purpose, not explicit routing.

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