Onda MCP

by mindfullabai

Overview Schema Source Related Servers Discussions Admin

TypeScript

Local

onda_workspace_create

Create a new workspace to group terminal tabs by project, using a name, root path, and optional color.

Instructions

Create a new workspace. Workspaces group tabs by project.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "name": "<name>",
      "rootPath": "<rootPath>"
    },
    "name": "onda_workspace_create"
  }
}

Input Schema

Name	Required	Description
`name`	Yes	Workspace name.
`color`	No	Color hex code (e.g., #a78bfa).
`rootPath`	Yes	Root directory path for the workspace.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.3.2Aug 10, 2026

TDQS

B3.4/5.0

Behavior2/5

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

With no annotations provided, the description carries the full burden for behavioral disclosure. It indicates the tool creates a workspace, but it does not disclose side effects, permissions required, behavior if the workspace already exists, or whether rootPath must exist beforehand. This is a significant gap for a mutation operation.

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?

The description consists of two concise sentences that efficiently state the action and purpose. There is no wasteful or redundant content.

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

Completeness2/5

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

The description is too sparse given the lack of annotations and output schema. It does not explain what the tool returns after creation, any prerequisites like directory existence, or error scenarios. While the schema covers parameters, the overall behavioral context is incomplete for an agent to invoke the tool safely and correctly.

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 description coverage is 100%, so each parameter already has a description. The tool description adds minimal value beyond that, only contextualizing workspaces as groupings of tabs by project. It does not elaborate on parameter syntax or constraints beyond the schema.

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

Purpose5/5

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

The description clearly states a specific verb and resource: 'Create a new workspace.' It also adds context ('Workspaces group tabs by project') that distinguishes this from sibling tools like workspace_list or workspace_focus, which perform different operations.

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

Usage Guidelines3/5

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

The description implies usage context by explaining the purpose of workspaces, but it does not explicitly state when to use this tool versus alternatives, nor does it mention exclusions or prerequisites. Sibling tools like workspace_list or workspace_focus are not referenced.

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