Export a read-only workflow pack containing personas, tools, turnstiles, and stacks. Use it to back up or transfer Msty Studio configurations without modifying source data.
Export a read-only workflow pack (personas, tools, turnstiles, stacks, …).
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | ||
| include | No |
| Name | Required | Description | Default |
|---|---|---|---|
| result | Yes |
Changes observed during successful MCP inspections.
v6.1.5Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden. 'Read-only' hints at a non-mutating artifact and the parenthetical lists contents, but the description omits permissions, side effects (such as whether it writes a file), and any rate or size limits.
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 front-loaded sentence with no filler. The trailing ellipsis makes it slightly vague, but it is otherwise efficient.
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, so return values need not be explained. However, with no annotations and 0% parameter description coverage, the description leaves the agent without guidance on include/limit behavior or export scope, which is too thin for a tool with two filter parameters.
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?
Schema description coverage is 0% and the description never mentions 'limit' or 'include'. The parenthetical categories may loosely hint at valid include values, but syntax, default behavior, and the limit parameter remain unexplained.
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 specific verb ('Export') and resource ('workflow pack'), with a parenthetical enumerating what's included. It is distinguishable from export_tool_config by resource scope, though it does not explicitly name the alternative.
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?
No when-to-use guidance, no prerequisites, and no alternatives are mentioned (e.g., export_tool_config). Usage is only implied by the verb 'Export'.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.