Skip to main content
Glama
Sign In
Minecraft Structure Lab

Minecraft Structure Lab

by ewitulsk
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

list_captures

List labeled screenshot metadata for a given revision, showing capture details without loading image data. Use to browse available captures before selecting one to retrieve.

Instructions

List labeled screenshot metadata without returning all image bytes.

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": {
      "revision": "<revision>"
    },
    "name": "list_captures"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
offsetNo
revisionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description must convey behavioral traits. It mentions that image bytes are not returned, which is helpful, but it does not disclose whether the operation is read-only, any side effects, pagination behavior, or rate limits.

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 description is a single, focused sentence with no unnecessary words or redundancy. It is well-structured and immediately conveys the core purpose.

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?

Given the tool has 3 parameters, no output schema, and no annotations, the description is too sparse. It does not explain parameter meanings, expected output structure, pagination mechanics, or how this tool fits into common workflows. The agent may struggle to use it correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema has 0% description coverage. The description does not explain any of the parameters (limit, offset, revision, with revision required). Since the schema only provides names and types, the lack of explanation leaves the agent without enough guidance for correct invocation.

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 tool's action (list), the resource (labeled screenshot metadata), and a distinguishing behavior (without returning all image bytes). This differentiates it from sibling tools like get_capture, which likely returns full images.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The phrase 'without returning all image bytes' implies when to use this tool (when metadata only is needed) and contrasts with tools that return full images. However, it does not explicitly name alternatives or provide more detailed selection criteria.

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

Deploy Server

Other Tools