Skip to main content
Glama
Sign In
anythingllm-mcp

anythingllm-mcp

by jbowensii
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

create_workspace

Creates a new AnythingLLM workspace by name, so you can separate chats, documents, and embeddings by project or team.

Instructions

Create a new workspace by name (AnythingLLM derives the slug).

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations, so the description carries the full behavioral burden for a mutation tool. It adds one useful detail (AnythingLLM derives the slug, so no slug input is needed), but says nothing about permission requirements, duplicate-name handling, reversibility, or what the response contains.

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?

One sentence, front-loaded with the action and resource, and every clause earns its place by clarifying the name/slug relationship.

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?

For a mutation tool with no annotations and no output schema, the description omits auth needs, error behavior on duplicate names, and what the created workspace returns. The one parameter is minimally covered, leaving an agent to guess at failure modes.

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?

Schema coverage is 0% with a single required string 'name', so the description must compensate. It does clarify that this string is the workspace display name and that the slug is derived rather than supplied, but adds no format, length, or uniqueness constraints.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb ('Create') and resource ('workspace') with the identifying input ('by name'). The verb set across siblings (get/update/delete_workspace) makes the action unambiguous, though the description never names a sibling or scope boundary explicitly.

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?

No guidance on when to use this versus update_workspace or how it relates to list_workspaces/get_workspace. There is no mention of prerequisites (auth, plan limits) or the alternative of creating with pre-set settings.

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