Skip to main content
Glama
bedrock-map-builder-mcp

bedrock-map-builder-mcp

by xRookieFight

op_list

Read-only

Lists the project's world edit history newest first, showing each operation's status (done, partial, failed, undone) and whether it can be undone.

Instructions

Journal of world edits in this project, newest first, with status (done, partial, failed, undone) and whether they can be undone.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "op_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, so the safety profile is covered; the description adds real behavioral detail beyond that by enumerating the status values (done, partial, failed, undone) and the newest-first ordering. It does not state pagination behavior or what an empty journal returns.

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 that carries the ordering and the two key result fields with no filler; every clause earns its place.

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 no output schema, the description must carry return semantics, and it does so partially by listing status values; however it omits the limit/paging contract and any hint about entry granularity, leaving a read tool with one undocumented parameter only partly specified.

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

Parameters2/5

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

Schema description coverage is 0% and the single parameter (limit, default 30, max 500) is never mentioned in the description, so an agent gets no explanation of result-set sizing or truncation from either source beyond bare type constraints.

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?

The description names a specific resource (journal of world edits) with scope and ordering (newest first), plus the fields returned (status, undoability). That is far more than a restatement of the name, though it does not explicitly name a sibling to contrast with.

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 rather than stated: 'whether they can be undone' hints that this is the review step before op_undo, but the description never says when to call it or when a different listing tool (plan_list, world_list) is the better choice.

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