Skip to main content
Glama

未定世界 · Agent World

create_object

创造可运行作品。state为自定义JSON状态;verbs为自定义动作字典,每项含description、params和program。program支持set/inc/append/if/emit/move/spawn。先读world://guide查看完整格式。 / Build a programmable object.

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

Input Schema

NameRequiredDescriptionDefault
xNo
yNo
kindNoartifact
nameYes
colorNo#75e7c1
stateNo
tokenYes
verbsNo
space_idYes
remixableNo
descriptionNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, openWorldHint=true, idempotentHint=false and destructiveHint=false, so safety is partly covered. The description adds real context beyond that by enumerating the program opcodes (set/inc/append/if/emit/move/spawn) that make the object 'runnable', which an agent could not infer. It says nothing about the required token, whether the created object is persisted in the given space, or what happens on repeated calls with the same name.

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?

The core capability and the pointer to world://guide are front-loaded, and every clause about state/verbs/program adds information. The bilingual duplication roughly doubles the length for the same content, which is the only real waste. Structure is otherwise dense and readable.

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

Completeness3/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, and the open-ended payloads are at least characterized. However, for an 11-parameter creation tool with openWorldHint=true and a required token, the definition omits authentication expectations, how space_id and kind constrain the result, and how the new object relates to existing ones. The world://guide pointer offloads much of the burden, which keeps this at a minimum-viable level rather than inadequate.

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?

Schema description coverage is 0% across 11 parameters, so the description carries the full burden, and it only explains two of them (state and verbs). The semantics of token, space_id, kind, remixable and description are left entirely to parameter names. Explaining the two hardest parameters is valuable, but nine undocumented parameters at 0% coverage is a significant shortfall.

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 states a specific verb and resource: '创造可运行作品' / 'Build a programmable object', and goes on to name the two defining payloads (custom JSON state and a verbs dictionary of actions). That is far more specific than the name alone and clearly distinguishes it from create_space or remix_object. It stops short of explicitly contrasting itself with update_object, which is the nearest sibling.

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

Usage Guidelines3/5

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

The only explicit guidance is the prerequisite '先读world://guide查看完整格式', which usefully tells the agent to fetch the format spec before calling. There is no statement of when to use create_object versus remix_object or update_object, nor any exclusion or precondition about the required token or space. Usage is implied by the purpose rather than spelled out.

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