gisgp

bundle_migration_readiness

PAID (100 credits) — migration-readiness report comparing two FeatureServer layers: schema diff, coded-value domains, and field types for both. Replaces compare_schemas + extract_domains×2 + check_field_types×2. Requires Authorization: Bearer <api_key> and sufficient credits balance.

Returns JSON: {ok, schema_diff, domains_a, domains_b, fields_a, fields_b,
ready, blockers} — ready is False and blockers lists the reasons if the
schema diff finds added/removed/changed fields or a geometry mismatch.

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": {
      "service_url_a": "<service_url_a>",
      "service_url_b": "<service_url_b>"
    },
    "name": "bundle_migration_readiness"
  }
}

Input Schema

Name	Required	Description	Default
`token_a`	No
`token_b`	No
`service_url_a`	Yes
`service_url_b`	Yes

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

AddedAug 8, 2026

TDQS

A4.4/5.0

Behavior5/5

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

No annotations are provided, so the description carries the full burden. It transparently discloses the cost (100 credits), authentication requirement, and the precise behavior of the ready and blockers fields when schema mismatches occur. This goes beyond typical descriptions.

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?

Two information-dense paragraphs with front-loaded cost and purpose. Every sentence adds value: purpose, replacement, auth/cost, return JSON structure, and condition for ready/blockers. No wasted words.

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?

The description covers purpose, replacement, auth, cost, return format, and ready/blockers logic. However, it omits explanation of token_a/token_b parameters and their relationship to the Authorization header, which is a significant gap for a complex bundle tool with no annotations.

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 does not explain the parameters. It implicitly refers to 'two FeatureServer layers' but does not name service_url_a/service_url_b or clarify the purpose of token_a/token_b, especially given the Authorization: Bearer requirement. The description fails to compensate for the schema gap.

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 purpose: 'migration-readiness report comparing two FeatureServer layers: schema diff, coded-value domains, and field types for both.' This is a specific verb+resource and distinguishes it from siblings by being a bundle that replaces multiple existing tools.

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

Usage Guidelines5/5

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

Explicitly says 'Replaces compare_schemas + extract_domains×2 + check_field_types×2', providing clear guidance on when to use this tool instead of alternatives. Also mentions the prerequisites: Authorization header and sufficient credits balance.

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

All gisgp tools Inspect

Try in Browser

Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.