MCP Minecraft Remote

Overview Schema Source Related Servers Discussions Admin

tradeWithVillager

Initiate a trade with a nearby villager by specifying the trade index and count. Optionally identify the villager by name.

Instructions

Trade with a nearby villager

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": {
      "tradeIndex": "<tradeIndex>"
    },
    "name": "tradeWithVillager"
  }
}

Input Schema

Name	Required	Description
`villagerName`	No	Name or identifier of the villager (optional)
`tradeIndex`	Yes	Index of the trade from listTrades (1-based)
`count`	No	Number of times to perform the trade

Schema Changelog

Changes observed during successful MCP inspections.

First observedAug 18, 2025

TDQS

B3/5.0

Behavior2/5

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

With no annotations, the description must convey behavioral traits like side effects on inventory or villager offers, but it only states a basic action, leaving much unknown.

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?

Extremely concise (4 words) but lacks structure; could include key context without being verbose.

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?

For a complex trading mechanic, the description is incomplete, omitting prerequisites, effects on trade stock, or outputs.

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 has 100% description coverage for parameters, so the description adds no extra meaning but is adequate; baseline 3.

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 clearly states the action ('Trade') and target ('villager'), distinguishing it from sibling tools like attackEntity or listTrades.

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?

No guidance on when to use this tool, such as needing to first call listTrades, or conditions like villager must be nearby.

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