list_export_adaptersLists available export adapters so you can identify supported narrative export formats, such as Ink or Yarn, before exporting a game story.
列出可用导出适配器
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v0.3.1Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description must carry the full burden. It doesn't disclose any behavioral traits beyond the implied read-only nature—no information on ordering, pagination, or what the adapters represent, and it doesn't clarify return format despite having no output schema.
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 clear, front-loaded phrase with no wasted words. It's appropriately sized for a simple listing tool.
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?
For a parameterless read-only tool, the description is minimally complete: it tells the agent what the tool does at a high level. However, with no output schema and no annotations, it doesn't explain return shape, ordering, or how adapters relate to export operations, leaving gaps an agent would notice.
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 this dimension uses the 0-param baseline of 4. There are no parameters whose semantics need explaining, and the schema is empty.
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+resource (list export adapters), which is clear on its own. The description is a single direct phrase, but it offers no differentiation from the vast set of sibling tools, many of which also 'list' resources (list_projects, list_scenes).
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 guidance on when to use this tool versus alternatives such as the 'export' sibling or other listing tools. The purpose is implied but the description provides no context, prerequisites, or exclusions.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.