Skip to main content
Glama
Sign In
Onda MCP

Onda MCP

by mindfullabai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

onda_workspace_focus

Switch to a specific workspace by ID to bring the correct terminal environment into focus for your current tasks.

Instructions

Switch to a workspace by ID.

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": {
      "id": "<id>"
    },
    "name": "onda_workspace_focus"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesWorkspace ID to switch to.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.2

TDQS

B3.2/5.0
Behavior2/5

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

With no annotations, the description carries the full burden of behavioral disclosure. It states 'Switch to a workspace by ID' but does not disclose any side effects, such as changing the active workspace context for subsequent tool operations, or what happens if the ID is invalid. This is a significant gap for a state-changing 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 is a single, clear sentence with no unnecessary words. It is front-loaded with the action and resource, making it highly scannable.

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?

While the tool is simple with only one parameter, the description lacks essential behavioral context. It does not explain the impact of switching focus, prerequisites (e.g., an existing workspace), or any interaction with the broader terminal/session context. For a state-changing tool, this is incomplete.

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?

The input schema already provides 100% coverage for the single 'id' parameter with a description ('Workspace ID to switch to.'). The tool description's 'by ID' adds no new meaning beyond the schema, so the baseline score of 3 is appropriate.

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 the action ('Switch to') and the resource ('a workspace') with a specific method ('by ID'). It distinguishes the tool from sibling workspace tools like list, create, or layout, making its purpose unambiguous.

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?

The description provides no guidance on when to use this tool versus alternatives. It does not mention that this should be used to change the active workspace or how it differs from workspace_focus-like operations in other domains. No exclusions or alternative tools are referenced.

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