Skip to main content
Glama
musharna

plant-genomics-mcp

by musharna

JASPAR: Motif Matrix

jaspar_motif
Read-onlyIdempotent

Retrieve a JASPAR binding profile by matrix ID, returning the raw position-frequency matrix plus TF class, species, and references. Provides complete motif details for downstream analysis or validation.

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 (a link for the client to fetch; no tool on this server retrieves it). 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 — a link for the client to open or fetch; no tool on this server dereferences it
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 — a link for the client to open or fetch; no tool on this server dereferences it

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.22.0
    • changedOutput schema / properties / sequence_logo / description
      Previous value: -"URL of the SVG sequence logo"New value: +"URL of the SVG sequence logo — a link for the client to open or fetch; no tool on this server dereferences it"
    • changedOutput schema / properties / web_url / description
      Previous value: -"JASPAR profile page"New value: +"JASPAR profile page — a link for the client to open or fetch; no tool on this server dereferences it"
  2. Addedv1.18.2

TDQS

A4.7/5.0
Behavior5/5

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

Beyond the readOnly/idempotent annotations, the description adds valuable behavioral details: the returned PFM structure keyed by A/C/G/T, the logo URL being a client-fetched link rather than server-retrieved, version resolution semantics, and typed NotFoundError behavior for unknown ids. These are not inferable from annotations or schema alone.

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?

Two dense but well-organized sentences front-load the primary behavior, then enumerate return contents, routing context, id semantics, and error behavior. Every clause provides selection-relevant information with no filler.

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?

For a single-parameter read-only tool with a rich output schema, the description covers the essential call semantics, id variants, return scope, an important caveat about the logo URL, and failure behavior. Nothing needed to invoke it correctly 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 coverage is 100% and the schema already documents the id format and versioning with 'MA0570.1 or MA0570 (latest version)'. The description repeats this idea with slightly more explicit wording about resolving to the newest version, but adds no substantively new meaning beyond the schema.

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 opens with a specific action and resource: 'Fetch one JASPAR binding profile by matrix id'. It also names the sibling tool tf_binding_motifs and distinguishes itself by returning the raw matrix, so an agent can select it unambiguously.

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 explicitly frames the tool as the 'drill-down companion' to tf_binding_motifs and states the exact difference: tf_binding_motifs returns derived consensus but not the matrix. This tells the agent when this tool is the right choice versus the sibling.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.