Retrieve producer-oriented knowledge profiles for Ableton's foundational factory devices. Use this to access curated information on built-in instruments and effects without manual lookup.
List producer-oriented knowledge profiles for foundational Ableton factory devices.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v0.3.1Output schema / additionalPropertiesRemoved value: -trueOutput schema / anyOfAdded value: +[
+ {
+ "properties": {
+ "profiles": {
+ "items": {
+ "properties": {
+ "family": {
+ "type": "string"
+ },
+ "id": {
+ "type": "string"
+ },
+ "name": {
+ "type": "string"
+ },
+ "notes": {
+ "items": {
+ "type": "string"
+ },
+ "type": "array"
+ },
+ "parameterRoles": {
+ "items": {
+ "type": "string"
+ },
+ "type": "array"
+ },
+ "type": {
+ "type": "string"
+ }
+ },
+ "required": [
+ "id",
+ "name",
+ "type",
+ "family",
+ "parameterRoles"
+ ],
+ "type": "object"
+ },
+ "type": "array"
+ }
+ },
+ "required": [
+ "profiles"
+ ],
+ "type": "object"
+ },
+ {
+ "properties": {
+ "error": {
+ "properties": {
+ "message": {
+ "type": "string"
+ },
+ "outcome": {
+ "enum": [
+ "unknown",
+ "not_executed"
+ ]
+ }
+ },
+ "required": [
+ "message",
+ "outcome"
+ ],
+ "type": "object"
+ }
+ },
+ "required": [
+ "error"
+ ],
+ "type": "object"
+ }
+]Output schema / propertiesRemoved value: -{
- "profiles": {
- "items": {
- "additionalProperties": true,
- "properties": {
- "family": {
- "type": "string"
- },
- "id": {
- "type": "string"
- },
- "name": {
- "type": "string"
- },
- "notes": {
- "items": {
- "type": "string"
- },
- "type": "array"
- },
- "parameterRoles": {
- "items": {
- "type": "string"
- },
- "type": "array"
- },
- "type": {
- "type": "string"
- }
- },
- "required": [
- "id",
- "name",
- "type",
- "family",
- "parameterRoles"
- ],
- "type": "object"
- },
- "type": "array"
- }
-}Output schema / requiredRemoved value: -[
- "profiles"
-]v0.3.0Input schema / requiredRemoved value: -[]Output schema / (root)Previous value: -nullNew value: +{
+ "additionalProperties": true,
+ "properties": {
+ "profiles": {
+ "items": {
+ "additionalProperties": true,
+ "properties": {
+ "family": {
+ "type": "string"
+ },
+ "id": {
+ "type": "string"
+ },
+ "name": {
+ "type": "string"
+ },
+ "notes": {
+ "items": {
+ "type": "string"
+ },
+ "type": "array"
+ },
+ "parameterRoles": {
+ "items": {
+ "type": "string"
+ },
+ "type": "array"
+ },
+ "type": {
+ "type": "string"
+ }
+ },
+ "required": [
+ "id",
+ "name",
+ "type",
+ "family",
+ "parameterRoles"
+ ],
+ "type": "object"
+ },
+ "type": "array"
+ }
+ },
+ "required": [
+ "profiles"
+ ],
+ "type": "object"
+}v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is fully covered. The description adds only the scope ('producer-oriented', 'foundational factory devices'), which tells the agent this is a curated static knowledge list rather than live device state — useful but modest, with no note on completeness, pagination, or whether third-party devices are excluded.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
A single compact sentence with the scope front-loaded and no filler. It could have used its few remaining words to define 'profile' or name a sibling instead of stopping at the resource noun phrase.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
An output schema exists and there are no parameters, so the description needn't explain return values or inputs. What is still missing is the one thing structure can't convey: what a 'producer-oriented knowledge profile' actually distinguishes (e.g., device character/use-case guidance vs. parameter data) and whether the list is exhaustive over factory devices.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The tool takes zero parameters, so there is nothing for the description to explain and the baseline is 4. Nothing in the description misdescribes or implies hidden filtering arguments.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a clear verb ('List') and a specific resource ('producer-oriented knowledge profiles for foundational Ableton factory devices'), which separates it from siblings like get_factory_device_context (single-device context) and list_producer_chain_blueprints (chain blueprints). The word 'profiles' is somewhat undefined, so an agent still can't tell exactly what content each item holds without inspecting the output schema.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description gives no explicit when-to-use guidance and names no alternatives. With many adjacent factory tools present (get_factory_device_context, get_factory_coverage, get_factory_browser_items, list_producer_chain_blueprints), the agent is left to infer the boundary between 'profiles' and those siblings.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.