Skip to main content
Glama

world_place_many

Create 1 to 10 entities in one call. Each entity's parent is either an entity id that already exists or the index of an earlier entity in the same list; the batch is sent as one request per depth level, so a parent that is an index is built first. Returns one line per entity: index -> id.

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": {
      "entities": "<entities>"
    },
    "name": "world_place_many"
  }
}

Input Schema

NameRequiredDescriptionDefault
roomNo
entitiesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

No annotations, so the description carries the full burden. It usefully discloses batching behavior (one request per depth level, parents built first) and the return format, but is silent on the failure semantics that matter most for a batch write: is the batch atomic, what happens to earlier entities if one fails, and what permissions are needed.

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 dense sentences, front-loaded with the create scope, then the parent-resolution rule, then the return shape. No filler; only the return-format sentence could be considered optional given there is no output schema.

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?

For a dependency-aware batch mutation with zero annotation coverage and an opaque item schema, ordering and return format are covered well. Missing are the entity object shape, the room parameter's meaning, and partial-failure behavior, which an agent needs before calling it on real data.

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% and the entities array items are fully open (additionalProperties: {}), so the schema explains nothing. The description does add genuine meaning about the parent field (existing id vs. index of an earlier entry), but it never describes what fields an entity carries or what the room parameter selects, leaving half the surface undocumented.

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 and resource ("Create ... entities") plus a hard scope ("1 to 10 ... in one call"), which implicitly separates it from a single-create sibling like world_place. It never names the singular alternative, so sibling differentiation is inferred rather than stated.

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 ordering rule ("a parent that is an index is built first") tells the agent when index-based parents are legal, which is real usage context. But there is no explicit when-to-use/when-not guidance and no naming of an alternative for single-entity creation or for entities whose parents already exist.

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.