gisgp

export_geojson_to_excel

PAID (80 credits) — convert a GeoJSON FeatureCollection to an Excel workbook (.xlsx, base64-encoded). Point geometries get LATITUDE/LONGITUDE columns; other geometry types get a GEOMETRY_WKT column. Separate from the web app's own Excel export (AGOL-service-tied, quota-gated there). Requires Authorization: Bearer <api_key> and sufficient credits balance. Returns JSON: {ok, xlsx_base64, feature_count}.

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": {
      "geojson": "<geojson>"
    },
    "name": "export_geojson_to_excel"
  }
}

Input Schema

Name	Required	Description	Default
`geojson`	Yes

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

AddedJul 29, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Discloses paid usage, credit cost, auth requirements, output format (base64-encoded xlsx), and return structure. No mention of error cases or rate limits, but fair given no annotations.

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?

Concise, front-loaded summary, uses bullet-point-like structure without clutter. Every sentence adds value.

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?

Covers core behavior, output schema exists for return values, and description adds feature_count. Missing error handling, validation, or more parameter details, but acceptable for this complexity.

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 coverage is 0%; description only names 'geojson' but does not explain expected format, size limits, or that it must be a string. Schema provides type 'string' but description adds no extra meaning.

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?

Description uses specific verb 'convert' and resource 'GeoJSON FeatureCollection to Excel workbook', distinguishes from other export tools (export_geojson_to_pdf, etc.) and explicitly handles geometry types.

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?

Clearly states it's paid (80 credits), requires auth and sufficient balance, and distinguishes from web app's Excel export. Lacks explicit when-not-to-use vs. alternatives like geojson_to_csv.

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.