gisgp

compare_schemas

Compare the field schemas of two ArcGIS FeatureServer layers.

Returns JSON diff: {added, removed, changed:[{field, diffs}], same,
geometry_match, identical} — useful for QA before an import or migration.

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

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.

First observedJul 11, 2026

TDQS

B3.3/5.0

Behavior2/5

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

With no annotations, the description must fully disclose behavior. It describes the output structure but omits critical behavioral traits such as read-only nature, authentication needs (tokens), error handling, or rate limits. The return type is given but not how the tool behaves in edge cases.

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 sentences: first states purpose, second describes output and use case. No unnecessary words, front-loaded with key information. Every sentence earns its place.

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 4 parameters (2 required) and no schema descriptions, the description is insufficient. It lacks details on token handling, URL format, prerequisites (e.g., layer must be FeatureServer), and fails to fully explain the JSON diff structure. An output schema exists but is not referenced.

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?

Schema description coverage is 0%, yet the description does not explain any parameter. It only implicitly refers to the two service URLs but provides no details on token parameters or their purpose. The description adds minimal value beyond parameter names.

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 compares field schemas of two ArcGIS FeatureServer layers, with a specific verb (compare) and resource (schemas). It distinguishes from siblings by its focus on schema comparison rather than geometry or data content.

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 description mentions 'useful for QA before an import or migration,' providing clear context for when to use. However, it does not explicitly state when not to use it or differentiate from alternatives like geojson_diff.

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.