Skip to main content
Glama
musharna

plant-genomics-mcp

by musharna

JASPAR: TF Binding Motifs

tf_binding_motifs
Read-onlyIdempotent

Fetch curated transcription-factor DNA binding motifs for a plant locus from JASPAR. Resolves the locus to UniProt and gene symbol, returns confirmed motifs with IUPAC consensus, assay type, and sequence logo.

Instructions

Fetch curated transcription-factor DNA binding motifs for a locus from JASPAR (jaspar.elixir.no; free, no key) — the cis-regulatory view. Resolves the locus → UniProt accession + gene symbol, searches JASPAR by symbol scoped to the organism's taxid, then CONFIRMS each candidate by matching the accession against the profile's uniprot_ids. Returns per motif the JASPAR matrix id, TF class/family, assay type (SELEX / ChIP-seq / PBM / DAP-seq), an IUPAC consensus derived from the position-frequency matrix (e.g. CACGTG, the G-box/ABRE core), motif length, PubMed refs, and an SVG sequence-logo URL. IMPORTANT: JASPAR's name search is fuzzy, so name-similarity hits belonging to a DIFFERENT gene are returned separately in name_only_matches and must NOT be attributed to this locus; only motifs is UniProt-confirmed. found=false means the gene has no curated profile (not a TF, or its family is unprofiled for that species) — a normal outcome, not an error. Use jaspar_motif to retrieve the raw matrix for any matrix_id. Coverage is Arabidopsis-heavy (1236 profiles) and thin elsewhere (maize 131, soybean 91, wheat 58, tomato 51, rice 10; Brachypodium and sorghum have none). Defaults to arabidopsis_thaliana; pass organism= for other species.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
locusYese.g. AT2G46830 (Arabidopsis CCA1), Os01g0100100 (rice RAP-DB)
organismNoPlant organism — accepts canonical slug (arabidopsis_thaliana), scientific or common name, or NCBI taxidarabidopsis_thaliana

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
foundYesTrue if any profile was UniProt-confirmed for this locus
locusYes
motifsNoUniProt-confirmed binding profiles
tax_idYesNCBI taxid the JASPAR search was scoped to
accessionYesResolved UniProt accession
truncatedYesTrue if the motif list was capped
motif_countYesTotal confirmed profiles (pre-cap)
name_only_matchesNoName-similarity hits belonging to a DIFFERENT gene [{matrix_id, name, uniprot_ids}] — not this locus's motifs
gene_names_searchedNoGene symbols used as JASPAR search keys
Behavior5/5

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

The description discloses many behavioral traits beyond annotations: it resolves locus to UniProt, confirms hits by accession matching, returns name_only_matches separately, explains coverage biases, and clarifies normal outcomes. Annotations only provide basic hints.

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 description is well-structured and front-loaded with the core purpose. Every sentence adds value, explaining the process, important caveats, and usage. It is concise given 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?

The description covers all key aspects: what the tool does, how it works, what is returned, important behavioral notes, coverage limitations, and relation to siblings. The existence of an output schema complements the description.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema covers both parameters with descriptions. The description adds meaning by explaining the default organism, accepted formats, and providing locus examples. This enriches the semantic understanding.

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 clearly states the tool fetches curated transcription-factor DNA binding motifs for a locus from JASPAR. It specifies the source, the process, and what is returned, and distinguishes from sibling tool jaspar_motif.

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?

The description provides guidance on when to use this tool by noting that jaspar_motif is for raw matrices, and explains that found=false is a normal outcome. It also contrasts with sibling tools implicitly. However, it does not explicitly list 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.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/musharna/plant-genomics-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server