@dropthis/mcp

Official

by dropthis-dev

Overview Schema Source Related Servers Discussions Admin

TypeScript

Hybrid

Switch workspace

dropthis_use_workspace

Idempotent

Switch the active workspace for this connection, directing subsequent publishes there. The choice persists across reconnects.

Instructions

Switch the active team/workspace for this connection. Subsequent publishes land in it; the choice persists server-side across reconnects. Use dropthis_workspaces to list available workspaces first.

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": {
      "workspace": "<workspace>"
    },
    "name": "dropthis_use_workspace"
  }
}

Input Schema

Name	Required	Description	Default
`workspace`	Yes	The workspace slug or id to switch to.

Output Schema

Name	Required	Description	Default
`id`	No
`kind`	No
`name`	No
`role`	No
`slug`	No
`isActive`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.37.0Aug 6, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations include idempotentHint and destructiveHint, but the description adds valuable behavioral context: the switch persists server-side across reconnects and affects subsequent publish operations. This goes beyond the structured hints.

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?

Two sentences, front-loaded with purpose, then consequences and guidance. Zero filler; every sentence earns its place.

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

Completeness5/5

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

For a one-parameter tool with an output schema, the description covers purpose, side effects, persistence, and pre-requisite listing. Complete for an agent to invoke 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?

The single parameter 'workspace' is fully described in the schema (slug or id). The description adds a hint to list workspaces first, but doesn't add new parameter-level details; baseline 3 due to high schema coverage.

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 opens with a specific verb ('Switch') and resource ('active team/workspace'), clearly distinguishing it from sibling tools like dropthis_workspaces (list) or dropthis_create_workspace. It unambiguously states the tool's function.

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

Usage Guidelines5/5

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

Explicitly instructs to list workspaces first via dropthis_workspaces, and explains when switching matters ('Subsequent publishes land in it'). This provides clear context for when to use this tool versus alternatives.

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