Skip to main content
Glama

Get block

get_block
Read-onlyIdempotent

Returns the block ID at given X, Y, Z coordinates, such as 'minecraft:stone', without block states, so agents can identify blocks in the Minecraft world.

Instructions

Return the block id at one position, e.g. 'minecraft:stone' (block states are not included).

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": {
      "x": "<x>",
      "y": "<y>",
      "z": "<z>"
    },
    "name": "get_block"
  }
}

Input Schema

NameRequiredDescriptionDefault
xYesBlock X coordinate (east is +X).
yYesBlock Y coordinate (height; the overworld build range is -64 to 319).
zYesBlock Z coordinate (south is +Z).

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so the safety profile is covered. The description adds one genuinely useful caveat—block states are not included—which prevents an agent from expecting state data. It says nothing about missing/unloaded chunks or out-of-range behavior, so it is helpful but not rich.

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?

A single front-loaded sentence with the return type, the scope limit, and the important exclusion of block states. Zero filler.

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?

With an output schema present and 100% parameter coverage, the description only needs to convey purpose and notable limits, which it does. Only the lack of routing guidance toward get_blocks or get_height_map keeps it short of complete.

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?

All three coordinates are fully documented in the schema with axis orientation and range notes, so the baseline is 3. The description adds no coordinate semantics beyond the schema; its example ('minecraft:stone') describes output, not inputs.

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 ('Return the block id at one position') and pins down scope to a single position, which implicitly contrasts with the plural sibling get_blocks. It does not name an alternative explicitly, but the operation is unambiguous.

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?

The phrase 'at one position' hints that multi-block reads belong to a sibling like get_blocks, but no when-to-use or when-not-to-use guidance is stated. Usage is only implied by the scope wording.

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