PostFader V12 — FL Studio MCP Server

Overview Schema Source Related Servers Discussions Admin

atlas_get_product

Read-onlyIdempotent

Read a Plugin Atlas product by exact product_id to get its vendor, controls, adapters, evidence, and stock alternatives. Offline read-only catalog lookup.

Instructions

Read one Plugin Atlas product: vendor, controls, adapters, and alternatives.

Offline and read-only. Returns the product's knowledge, its control
adapters (which parameters mean what), evidence, and stock alternatives. An
adapter record does not prove that a loaded copy is writable; join catalog
knowledge to live targets with atlas_match_loaded.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`request`	Yes	Exact product_id from atlas_search, atlas_recommend, or atlas_match_loaded.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`vendor`	No
`product`	Yes
`adapters`	No	Descriptive catalog control mappings; these do not prove that a currently loaded instance exposes writable controls.
`evidence`	No	Catalog source references and compatibility or write-validation records; inspect each record's scope and provenance before generalizing it to a live target.
`schema_version`	No		1.0
`registry_digest`	Yes	SHA-256 identity of the bundled catalog used for this response.
`stock_alternatives`	No	Catalog FL Studio stock alternatives; this is not a claim of ownership or installation.

Schema Changelog

Changes observed during successful MCP inspections.

Addedv11.0.2Oct 5, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds genuine value beyond that with the caveat that an adapter record does not prove a loaded copy is writable, plus the offline framing and the contents of the returned knowledge.

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?

Four tight sentences with the purpose front-loaded and the caveat/alternative following. Minor overlap between 'knowledge' and the enumerated 'controls, adapters', but nothing is wasted.

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 explained, and the description still covers purpose, the key semantic caveat, and the sibling relationship. It is complete enough for an agent to call this correctly without opening the schema.

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 single product_id parameter is already well documented (exact id, not a display name). The description adds no syntax or format detail beyond the schema, so the baseline of 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Read one Plugin Atlas product') and enumerates the payload (vendor, controls, adapters, alternatives), which distinguishes it from the multi-result atlas_search/atlas_recommend siblings. It also names atlas_match_loaded as the related tool, though it does not explicitly contrast itself with atlas_search.

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?

Gives clear context ('Offline and read-only') and an explicit alternative for a related goal ('join catalog knowledge to live targets with atlas_match_loaded'). It does not spell out when-not-to-use conditions, but the routing to the sibling is concrete enough to be actionable.

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

Deploy Server