Skip to main content
Glama

Set villager profession

set_villager_profession
DestructiveIdempotent

Change a Minecraft villager's profession by entity UUID, resetting its current trades so it takes on new work such as librarian, farmer, or weaponsmith.

Instructions

Change a villager's profession. This resets the villager's current trades.

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>",
      "profession": "<profession>"
    },
    "name": "set_villager_profession"
  }
}

Input Schema

NameRequiredDescriptionDefault
uuidYesEntity UUID, e.g. as returned by summon_entity or get_players.
professionYesNew profession.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already flag destructiveHint=true and idempotentHint=true, but the description adds the crucial concrete consequence: existing trades are wiped. That is exactly the kind of disclosure annotations cannot convey. It still doesn't say whether the reset is reversible or what the response contains, but with output schema present that is a minor gap.

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?

Two short sentences, action first and the destructive side effect front-loaded immediately after. No redundant restatement of the title or schema.

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?

For a two-parameter mutation with an output schema and explicit destructive annotation, the definition covers what an agent needs: the effect and its cost. A caveat about whether the villager must be unemployed or whether the reset is permanent would complete it.

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 profession enum is self-explanatory, so the schema carries full parameter meaning. The description adds no extra detail such as whether 'none' leaves the villager unemployed or how uuid lookup failures behave, so baseline 3 applies.

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 ('Change') and resource ('a villager's profession'), which is unambiguous. The mention of trade reset also implicitly separates it from the sibling set_villager_trades, though it never names that sibling explicitly.

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?

Usage is implied by the described effect rather than stated: the trade-reset warning lets an agent infer it should avoid this when trades matter. There is no explicit when-to-use, when-not-to-use, or named alternative such as set_villager_trades for the trade-only case.

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