Skip to main content
Glama
Sign In

Antwork

by io.antwork
OverviewDiscussionsAdmin

create_workspace

Create a new workspace owned by the authenticated user.

Use this when the user wants a separate brand / client / project space — each workspace has its own connected social accounts, posts, and media library. Subsequent tool calls can target the new workspace by passing workspace_id (its returned ID or its name).

Args: name: Workspace name (required, 1–60 characters).

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>"
    },
    "name": "create_workspace"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes
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.
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: -[
-  "name",
-  "context",
-  "llm_model"
-]New value: +[
+  "name"
+]
  2. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint=false, destructiveHint=false, openWorldHint=false), and the description adds non-obvious context: the new workspace is bound to the authenticated user, it is isolated from other workspaces, and its returned ID is what subsequent calls should pass. It doesn't mention any failure modes such as duplicate names or limits on workspace count.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three short, front-loaded paragraphs: purpose first, selection guidance second, parameter constraint last. The "Args: name: Workspace name (required...)" line partially restates what the schema's required array already says, but it earns its place by adding the length bound.

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 an output schema present, the description needn't explain return values, and it still usefully notes that the returned ID is what later calls should use. For a simple single-required-parameter creation tool with annotations covering safety, this is nearly complete; only naming or capacity constraints for workspaces is missing.

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 coverage is 75%, and the one undocumented parameter in the schema (name) is the one the description covers, including the 1–60 character constraint that the schema itself lacks. The analytics-only parameters (context, llm_model, conversation_id) are already documented in the schema and are correctly left out.

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 and resource ("Create a new workspace") plus the ownership scope ("owned by the authenticated user"), and explains what a workspace contains (social accounts, posts, media library), which distinguishes it from list_workspaces and update_workspace without opening either schema.

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?

"Use this when the user wants a separate brand / client / project space" gives a concrete trigger condition, and it adds downstream guidance that later calls target the new workspace via workspace_id. It does not name an alternative or state when not to use it (e.g. reusing an existing workspace via list_workspaces).

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