Skip to main content
Glama

Set villager trades

set_villager_trades
DestructiveIdempotent

Replaces all trades on a Minecraft villager with a custom ordered trade list. Define item costs, sell rewards, max uses, and XP rewards using the villager UUID.

Instructions

Replace all of a villager's trades with custom ones.

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": {
      "uuid": "<uuid>",
      "trades": "<trades>"
    },
    "name": "set_villager_trades"
  }
}

Input Schema

NameRequiredDescriptionDefault
uuidYesEntity UUID, e.g. as returned by summon_entity or get_players.
tradesYesThe complete new trade list, in order.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior4/5

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

The annotations already declare destructiveHint=true and idempotentHint=true, but the description adds the important operational detail that the complete trade list is replaced, not appended to or partially edited. It still omits prerequisites such as whether the villager must exist or be loaded, and what happens on invalid trade data.

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?

The definition is a single front-loaded sentence with no filler. Every word contributes to specifying the replacement operation.

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?

With a rich input schema, an output schema, and destructive/idempotent annotations, the short description is nearly sufficient for correct invocation. However, it lacks prerequisite context, such as the villager needing to exist, and gives no guidance on empty trade lists or failure cases.

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 description coverage is 100%, and the nested Trade and TradeItem definitions richly document item ids, amounts, buy/sell semantics, max uses, and experience rewards. The description itself adds no parameter meaning beyond 'custom ones', so it meets the baseline of 3 rather than adding value beyond the schema.

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

Purpose5/5

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

The description states a specific verb, 'Replace', a precise resource, 'all of a villager's trades', and the scope, 'with custom ones'. This clearly distinguishes it from siblings such as get_villager or set_villager_profession without needing to open the schema.

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 explicit when-to-use, when-not-to-use, or alternative guidance. The agent must infer that get_villager might be used first to inspect existing trades and that this tool is for wholesale replacement rather than profession changes.

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