Skip to main content
Glama

jean — Molecular Biology & Genomics

scan_protein_domains

Read-only

De-novo protein domain and family annotation: submits a protein to EMBL-EBI InterProScan and returns every member-database signature that matches it — Pfam, CATH-Gene3D, SUPERFAMILY, PANTHER, PROSITE, SMART, CDD and the rest — with its InterPro entry, its GO terms, its coordinates and its E-value. This is the DOMAIN half of the Protein domains panel; for the short linear motifs a profile scan cannot see, use find_linear_motifs, which takes the domains this tool emits. The scan runs at EBI, takes minutes, and needs a contact address because EBI requires one.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
emailNoEBI requires a contact address on every submission (their abuse contact, not a login). Left empty, the one saved in any EMBL-EBI panel is used, which only the in-browser doors can read. It is sent to EBI with the job and stored nowhere by this tool.
_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.
sortByNorow order of the returned matches. Values: length (longest first), position (position along the protein), evalue (best E-value first), library (by member database).length
goTermsNoask InterPro to attach Gene Ontology terms to the integrated entries, so a match carries its function rather than only its accession.
proteinYesthe protein sequence, one-letter codes; wire it from translate_sequence or read it off a CDS.
_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.
pathwaysNoask InterPro to attach pathway cross-references (Reactome, KEGG, MetaCyc) to the integrated entries.
maxEvalueNodrop matches whose E-value is worse than this. 0 applies no threshold. A match the member database scores no E-value for (Coils, MobiDB-lite, Phobius) is KEPT either way — it has not failed the threshold, it was never scored against one.
applicationsNomember databases to run, comma-separated, using InterProScan's own ids (Pfam, Gene3D, SUPERFAMILY, PANTHER, PROSITE …). Empty runs the service's own default set, which is every database it has enabled. An id the live service does not advertise is refused by name rather than dropped.
integratedOnlyNokeep only signatures integrated into an InterPro entry, dropping member-database hits InterPro has not curated into one.
visibleLibrariesNokeep only matches from these member databases, comma-separated, as the RESULT document spells them (PFAM, GENE3D, SUPERFAMILY, CDD, PANTHER, MOBIDB_LITE …). This narrows what comes back; `applications` narrows what is RUN, and they are not the same question — a caller reading one library out of the service's default set wants this one. Empty keeps every database that answered.
representativeOnlyNokeep only the matches InterProScan itself marks representative — its own answer to “which of these overlapping signatures describes this region best”.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
countYesmatches returned, after the reading knobs
jobIdYesEBI's own job id, which is re-fetchable at their dispatcher for as long as they keep it — the provenance of this result, not an internal handle
domainsYesthe FOLDED regions only — domains, as `start-end@label` residue ranges — ready to wire straight into find_linear_motifs.domains so its globular-domain filter can bury motifs in them. Families, signal peptides, transmembrane helices, coiled coils and disordered spans are excluded: those are not folds a motif can hide inside, and disorder is where linear motifs live
matchesYesevery signature that matched, after the reading knobs: member database, signature accession and name, the InterPro entry it is integrated into, its kind (domain, family, site, repeat, homologous superfamily…), 1-based inclusive aaStart/aaEnd, the fragments a discontinuous domain is made of, the E-value and the GO and pathway cross-references
provenanceYesthe InterProScan version that ran, the MD5 the service computed over the sequence it analyzed, the member databases asked for, how many matches the scan returned before the reading knobs, and which of those knobs ran

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint=true, destructiveHint=false, openWorldHint=true), so the description is judged for added context. It adds real operational traits: the scan 'runs at EBI, takes minutes' (remote execution + latency) and 'needs a contact address because EBI requires one' (a submission constraint). It does not, however, discuss failure modes or what happens on EBI-side rejection.

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?

Three dense sentences, front-loaded with the action and scope, then the sibling routing, then the operational caveat. Nearly every clause earns its place, though the long database enumeration and 'and the rest' are slightly padded.

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?

Despite 12 parameters and nested objects, the description supplies everything an agent needs beyond structured fields: the remote/long-running nature, the mandatory contact address, and the downstream chaining to find_linear_motifs. Return values are covered by the output schema, so nothing essential 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% and the schema itself is unusually explicit (e.g. the applications vs visibleLibraries distinction, maxEvalue's E-value-less member handling). The description only reinforces the email requirement, which the schema already fully documents, so baseline 3 applies.

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+resource ('De-novo protein domain and family annotation', 'submits a protein to EMBL-EBI InterProScan') and enumerates the member databases returned (Pfam, CATH-Gene3D, SUPERFAMILY, PANTHER, PROSITE, SMART, CDD). It explicitly distinguishes itself from sibling find_linear_motifs by calling itself 'the DOMAIN half of the Protein domains panel'.

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

Usage Guidelines5/5

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

It names the alternative tool (find_linear_motifs) and the condition that selects it ('for the short linear motifs a profile scan cannot see'), including the data-flow relationship ('which takes the `domains` this tool emits'). This is an explicit when-to-use/when-to-use-something-else routing statement.

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