Skip to main content
Glama
Sign In
cp77wb-mcp

cp77wb-mcp

by 0xra0
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

wb_export_inspect

Validates and summarizes a World Builder *_exported.json file before conversion, so you can review contents and catch issues before importing.

Instructions

Validate/summarize a World Builder *_exported.json before conversion.

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": {
      "export_file": "<export_file>"
    },
    "name": "wb_export_inspect"
  }
}

Input Schema

NameRequiredDescriptionDefault
export_fileYes
importer_versionNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full burden. It does not state whether the tool is read-only, what validation rules it applies, what the summary contains, or what happens on invalid input.

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?

It is a single front-loaded sentence with no filler. The brevity is efficient, though it leaves important gaps that could have been addressed in one additional sentence.

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?

With no output schema, no annotations, and 0% parameter coverage, the description should explain what the summary includes and how importer_version affects validation. Instead it only states the broad purpose, leaving an agent without enough detail to use the tool confidently.

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 description never mentions either parameter. The meaning of importer_version, in particular, is left entirely unclear, including whether it changes validation behavior.

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 specific verbs (validate/summarize) and a specific resource (World Builder *_exported.json), with a workflow hint (before conversion). It does not explicitly differentiate itself from siblings such as wb_validate or wb_native_preflight.

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 'before conversion' implies when in the workflow to use it, but there are no explicit alternatives or exclusions. An agent must infer whether this is the right tool versus wb_validate or wb_native_preflight.

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