Skip to main content
Glama
Sign In
opentoonz-mcp

opentoonz-mcp

by c0d33ngr
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Opentoonz List Workspaces

opentoonz_list_workspaces

List all OpenToonz workspaces with their scenes and rendered videos to locate project assets.

Instructions

List workspaces with their scenes and rendered videos.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "opentoonz_list_workspaces"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.8.0

TDQS

B3.4/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It discloses the return content (workspaces, scenes, rendered videos), which is useful, but says nothing about read-only nature, side effects, pagination, or performance. 'List' implies a non-destructive read, which is a mild signal.

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?

A single front-loaded sentence with no filler, immediately conveying the resource and the nested content returned.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

No output schema and no annotations, so the description is the only source of truth. It sketches the return shape (workspaces with scenes and rendered videos) but omits output format details and any behavioral context; adequate for a trivial parameterless list tool, but with gaps.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters, so per the rubric the baseline is 4 with no schema semantics to compensate for. The description adds nothing here because there is nothing to add.

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 ('List workspaces') and adds scope by noting it returns scenes and rendered videos. This distinguishes it from narrow siblings like opentoonz_scene_info, though it doesn't explicitly contrast with other list/introspection tools such as opentoonz_health or opentoonz_doctor.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no guidance on when to use this versus alternatives. With many read/introspection siblings (scene_info, health, doctor) plus workspace mutation tools (create/delete), the description never says when listing workspaces is the right call or what prerequisites exist.

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

Deploy Server

Other Tools