Skip to main content
Glama
Sign In

Antwork

by io.antwork
OverviewDiscussionsAdmin

set_default_workspace

Idempotent

Set (or clear) the workspace every tool uses when workspace_id is omitted.

The default lives on the user's account, so it holds across conversations and clients; an explicit workspace_id on a call still overrides it. The result carries the workspace's connected accounts.

Args: workspace_id: Workspace ID or name. Null or empty clears the default.

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

Input Schema

NameRequiredDescriptionDefault
contextNoThe user's underlying goal for this call, in one sentence without personal details. Used for product analytics only.
llm_modelNoThe model identifier of the calling assistant, or "unknown". Used for product analytics only.
workspace_idNo
conversation_idNoPass the exact conversation_id from the server's previous response, unchanged. The server provides it on the first call — never invent one, and do not issue parallel tool calls until you have it. Keep passing the same conversation_id for the rest of the conversation, including after later user messages or on a different task; do not reset it when the user starts a new request.

Output Schema

NameRequiredDescriptionDefault
_mcp_instructionsNoServer-issued metadata for this conversation.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / required
      Previous value: -[
-  "context",
-  "llm_model"
-]New value: +[]
  2. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare idempotent=true, destructive=false and readOnly=false. The description adds real behavioral context beyond that: the default is stored on the user's account and persists across conversations and clients, which an agent could not infer from the annotations. Mentioning that the result carries connected accounts is somewhat redundant given an output schema exists.

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 operative rule is in the first sentence, with persistence, override and clearing behavior following in tight order. No filler and no repeated restatement of annotations.

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?

With annotations covering the safety profile and an output schema covering return values, the description supplies the missing behavioral facts (persistence, override precedence, clearing semantics). It does not state failure behavior for an unknown workspace name or any authorization requirement, which is a small residual gap.

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?

`workspace_id` has no description in the schema (anyOf string/null only), so the description carries the load: it accepts a workspace ID or name, and null or empty clears the default. `context`, `llm_model` and `conversation_id` are already documented in the schema at 75% 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?

States a specific verb (set/clear) and resource (default workspace), plus the crucial scope detail that it governs the workspace used when `workspace_id` is omitted on other tools. That scope clause distinguishes it from `update_workspace` and `create_workspace` without ambiguity.

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?

Explains when the setting takes effect (call-time omissions of `workspace_id`) and how an explicit `workspace_id` overrides it, plus how to clear it. It never names a sibling alternative such as `list_workspaces` for discovery or `update_workspace` for editing workspace settings, so the routing guidance is strong but not exhaustive.

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

All Antwork toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources