Skip to main content
Glama
musharna

plant-genomics-mcp

by musharna

JASPAR: Motif Matrix

jaspar_motif
Read-onlyIdempotent

Fetch a JASPAR transcription factor binding profile by matrix id, including position-frequency matrix, TF class, family, species, and references. Resolves versioned or base ids, returns error for unknown ids.

Instructions

Fetch one JASPAR binding profile by matrix id, including its raw position-frequency matrix (PFM: per-base count vectors keyed A/C/G/T) plus TF class/family, assay type, source species, UniProt accessions, PubMed refs, IUPAC consensus, and the sequence-logo URL. The drill-down companion to tf_binding_motifs, which returns the derived consensus but not the matrix. Accepts a versioned id (MA0570.1) or a bare base id (MA0570, which resolves to the newest version). Unknown ids raise a typed NotFoundError.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
matrix_idYesJASPAR profile id, e.g. MA0570.1 or MA0570 (latest version)

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
pfmNoPosition-frequency matrix: per-base count vectors keyed A/C/G/T
nameNoTF name as curated by JASPAR
lengthNoMotif width in bases
base_idNoVersion-less profile id, e.g. MA0570
speciesNoSource species [{tax_id, name}]
versionNoJASPAR release version of the profile
web_urlNoJASPAR profile page
tf_classNoStructural class, e.g. ['Basic leucine zipper factors (bZIP)']
consensusNoIUPAC consensus derived from the PFM, e.g. 'AAATATCT' (the Evening Element)
data_typeNoAssay the profile derives from: SELEX / ChIP-seq / PBM / DAP-seq
matrix_idNoJASPAR profile id, e.g. MA0570.1
tf_familyNoTF family, e.g. ['MYB-related']
collectionNoCORE / PBM / UNVALIDATED / …
pubmed_idsNoSupporting PubMed IDs
uniprot_idsNoUniProt accessions JASPAR attributes the profile to
sequence_logoNoURL of the SVG sequence logo
Behavior4/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, destructiveHint. The description adds behavioral details: how IDs are resolved (base ID resolves to newest version), and that unknown IDs raise a typed NotFoundError. No contradiction.

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?

Description is a single paragraph but efficiently conveys purpose, scope, companion tool, ID format, and error handling. Slightly dense but well-structured.

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 tool has an output schema, the description doesn't need to detail return values. It lists key data fields and covers ID format, companion tool, and error handling. Fully complete for this simple tool.

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

Parameters4/5

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

Schema coverage is 100% with description for matrix_id. The description adds meaning by explaining it accepts versioned (MA0570.1) or bare base IDs (MA0570, resolves to newest), which goes beyond the schema's type description.

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 a JASPAR binding profile by matrix id, listing specific data returned (PFM, TF class, etc.). It distinguishes itself from sibling tool tf_binding_motifs as the drill-down companion that returns the full matrix.

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 explicitly positions this tool as the drill-down companion to tf_binding_motifs, guiding when to use each. It also explains ID versioning (versioned vs base) and error behavior. No explicit when-not, but clear context.

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