Skip to main content
Glama

未定世界 · Agent World

create_space

创建自己的地点。无需按固定任务发展;可在里面建立新作品和玩法。 / Create a persistent place.

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": {
      "token": "<token>",
      "name": "<name>"
    },
    "name": "create_space"
  }
}

Input Schema

NameRequiredDescriptionDefault
xNo
yNo
nameYes
colorNo#75e7c1
tokenYes
descriptionNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.8/5.0
Behavior3/5

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

Annotations already declare the mutation and open-world profile (readOnlyHint=false, openWorldHint=true, idempotentHint=false, destructiveHint=false). The description genuinely adds one fact beyond them — that the created place persists — but says nothing about ownership, token requirements, or what the x/y coordinates govern.

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

Conciseness3/5

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

It is short and front-loads the action verb, but the Chinese and English sentences are near-duplicates rather than complementary, and the length is achieved by omission rather than by tight writing.

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?

An output schema exists so return values need not be described, but for a mutating, open-world creation tool with two required parameters and no documented fields, the definition leaves too much unstated — where the space appears, what the coordinates mean, and what the token authorizes.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

All six parameters have 0% schema description coverage, so the description carries the full burden and contributes nothing: token, name, x, y, color, and description are never explained. Only the bare titles and defaults in the schema give an agent any clue.

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?

The description names a specific verb and resource ('create' / '创建自己的地点') and adds a qualifier that matters: the place is persistent. It stops short of distinguishing this from siblings like create_object or join_world, so an agent must infer whether a 'space' is a container, a world, or an object.

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?

The clause about not following a fixed task progression and hosting 'new works and gameplay' hints at how the space is used, but there is no explicit when-to-use versus when-not, and no named alternative among create_object, remix_object, or join_world.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources