gecko-mcp

by Frumane

Overview Schema Source Related Servers Discussions Admin

TypeScript

Local

switch_workspace

Switch to a specific Floorp workspace by providing its workspace ID, enabling quick navigation between workspaces.

Instructions

Switch to a Floorp workspace by id (from list_workspaces). Floorp-specific.

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": "switch_workspace"
  }
}

Input Schema

Name	Required	Description	Default
`id`	Yes	Workspace id.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv2.2.4Jun 20, 2026

TDQS

A4.2/5.0

Behavior3/5

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

Annotations already indicate readOnlyHint=false and destructiveHint=false. Description adds Floorp-specific context but does not elaborate on side effects or behavior beyond the basic action.

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?

Single sentence with no wasted words. Directly conveys essential information.

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

Completeness4/5

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

For a simple one-parameter tool without output schema, description adequately covers what the tool does and where parameter comes from. Minor gap: no indication of error behavior.

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?

Schema has one parameter with basic description. The description adds 'from list_workspaces' which gives context on how to obtain the id, adding value beyond 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?

Clearly states action (switch to workspace), resource (workspace), and source of id (list_workspaces). Distinguishes as Floorp-specific, differentiating from siblings.

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

Usage Guidelines4/5

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

Implies using id from list_workspaces, providing clear context. No explicit exclusions or alternatives, but sufficient for a simple switch action.

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