Skip to main content
Glama

wb_generate_market

Generates a market grid of assets from a deterministic weighted pool, using rows, columns, and spacing for repeatable layouts. Runs as a dry run unless write=true is set.

Instructions

Generate a market grid from a deterministic weighted asset pool. Dry-run unless write=true.

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": {
      "file": "<file>",
      "parent": "<parent>",
      "catalog": "<catalog>",
      "pool": "<pool>",
      "rows": "<rows>",
      "columns": "<columns>",
      "spacing_x": "<spacing_x>",
      "spacing_y": "<spacing_y>"
    },
    "name": "wb_generate_market"
  }
}

Input Schema

NameRequiredDescriptionDefault
xNo
yNo
zNo
fileYes
nameNo
poolYes
rowsYes
seedNo
writeNo
parentYes
catalogYes
columnsYes
spacing_xYes
spacing_yYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

B3.1/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose two valuable traits: generation is deterministic/weighted and it is a dry run unless write=true. It does not say what a dry run returns, whether an existing file at `file` is overwritten, or what permissions/state the write path touches.

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?

Two tight, front-loaded sentences with no filler; the core action comes first and the write caveat second. It is arguably under-specified for a 14-parameter tool, but nothing is wasted.

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?

Placeholder check: actual score 2. For a tool with 14 parameters (8 required), no annotations, and no output schema, this definition leaves too much unresolved — the meaning of the required `file`/`parent`/`catalog` triple and the layout parameters are undocumented in both schema and prose.

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 14 parameters, so the description must compensate and largely fails: only `pool` and `write` get any meaning, and `seed` is hinted at via "deterministic." Nothing explains `file`, `parent`, `catalog`, `name`, `x`/`y`/`z`, rows/columns/spacing, or the relationship between the grid dimensions and the pool contents.

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 ("Generate a market grid") plus the source data shape ("deterministic weighted asset pool"), which separates it from generic siblings like wb_grid and from wb_generate_room/wb_generate_corridor. It stops short of naming those alternatives, and the domain term "market grid" is not defined anywhere.

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?

There is no statement of when to prefer this over wb_grid, wb_asset_pool_spawn, or the other wb_generate_* tools, nor any prerequisites (does `file`/`catalog` need to exist first?). The only guidance given is the write-mode default, which is a safety behavior rather than a selection criterion.

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