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

bedrock-map-builder-mcp

by xRookieFight

generator_help

Read-only

Lists available map generators, what each builds, and how origin is applied, or returns the full argument schema for a single generator.

Instructions

List the generators with what they build and how origin is used, or the full argument schema of one generator.

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": "generator_help"
  }
}

Input Schema

NameRequiredDescriptionDefault
generatorNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior4/5

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

The readOnlyHint annotation already establishes that this is a safe read operation. The description adds meaningful behavioral detail by stating what is returned in each mode: generator names with build and origin usage, or a single generator's full argument schema. It stops short of describing error handling for unknown generator names.

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 tightly written sentence with no filler. The primary listing behavior is front-loaded, and the alternative single-generator mode follows immediately.

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 simple read-only help tool with one optional parameter and no output schema, the description covers both invocation modes and the returned content well. The main remaining gaps are how unknown generator names are handled and any format details for the returned schema.

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

Parameters4/5

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

Schema description coverage is 0%, so the description must explain the lone optional 'generator' parameter. It does so reasonably well: omitting it lists generators, while supplying it returns that generator's full argument schema. It still does not specify valid identifier format or case sensitivity.

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 gives a specific verb ('List') and resource ('generators'), and explains the two output modes: list all generators with build/origin details, or show one generator's full argument schema. It clearly reads as a help/introspection tool rather than an execution tool, though it does not explicitly name or contrast itself with the sibling 'generate' tool.

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 two modes are implied by whether a generator argument is supplied, so an agent can infer how to get the list versus a single schema. However, there is no explicit guidance on when to use this help tool before calling 'generate', nor any stated exclusions or prerequisites.

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