Skip to main content
Glama

Get villager

get_villager
Read-onlyIdempotent

Fetch a Minecraft villager's profession, level, available trades, and trade use limits by entity UUID.

Instructions

A villager's profession, level and trades (with uses and limits).

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

Input Schema

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

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered without the description. The parenthetical "with uses and limits" does add a small amount of useful return-content context (trades carry remaining-use counters), but nothing about failure modes, e.g. what happens for a non-villager or offline entity.

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?

A single short clause with zero waste and no filler; the most important information (profession, level, trades) leads. It loses a point only for being a sentence fragment rather than a purposeful statement.

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 one fully documented required parameter, an output schema, and complete annotations, the definition's burden is light and it mostly meets it by naming the returned fields. Still missing is any framing that this is a targeted read of entity data and how it relates to get_entity.

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 100%: the single uuid parameter is documented with a regex pattern and an example pointing at summon_entity / get_players. The description adds nothing to parameter meaning, so the baseline 3 applies.

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

Purpose3/5

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

"A villager's profession, level and trades (with uses and limits)" names a specific resource and enumerates the fields returned, so an agent knows the payload's shape. However, it is a noun fragment with no verb (no "get"/"read"), and it never distinguishes this from get_entity, which could plausibly also return a villager's data. Specific about content, vague about the action.

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 when-to-use instruction, no prerequisites, and no mention of alternatives such as get_entity or the write-side siblings set_villager_profession / set_villager_trades. The agent must infer usage entirely from the tool name.

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