Skip to main content
Glama

convert_geoscience

Convert KML files to GeoJSON or JSON and GeoJSON to JSON for geospatial mapping, analysis, and data interchange workflows.

Instructions

Convert geoscience formats: KML→GeoJSON/JSON, GeoJSON→JSON. For advanced formats like NetCDF/HDF5/GeoTIFF/Shapefile, additional tooling is required and not currently handled by this server.

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": {
      "inputPath": "<inputPath>",
      "outputPath": "<outputPath>"
    },
    "name": "convert_geoscience"
  }
}

Input Schema

NameRequiredDescriptionDefault
variableNoVariable name to extract from NetCDF/HDF5 (optional)
inputPathYesAbsolute path to input geoscience file
outputPathYesAbsolute path for output file (include extension)
inputFormatNoInput format (auto-detected if not provided)
outputFormatNoOutput format

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.1.0

TDQS

A3.7/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full behavioral burden. It discloses an important limitation around advanced formats, but it does not explain whether output files are overwritten, what errors look like, file size limits, or other operational constraints. The format-support warning adds value, but more behavioral context is needed for a file-writing conversion tool.

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 two focused sentences with the supported conversions front-loaded and the unsupported-format caveat clearly separated. There is no unnecessary wording.

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?

For a conversion tool with five parameters, no annotations, and no output schema, the description covers the main format scope but leaves operational behavior unspecified. The mismatch between the stated unsupported formats and the schema's accepted enum values also weakens completeness.

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

Parameters3/5

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

Schema description coverage is 100%, so the schema already explains inputPath, outputPath, inputFormat, outputFormat, and variable. The description reinforces the supported format directions but does not add meaningfully beyond the schema, and it actually creates ambiguity by saying NetCDF/HDF5/GeoTIFF/Shapefile are not handled while the inputFormat enum includes them.

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 uses a specific verb ('Convert') plus the resource domain ('geoscience formats') and enumerates supported conversions such as KML→GeoJSON/JSON and GeoJSON→JSON. It is clear enough to distinguish this from generic convert_* siblings, though it does not explicitly name them.

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?

It clearly states which conversions this tool handles and warns that advanced formats like NetCDF/HDF5/GeoTIFF/Shapefile require additional tooling and are not currently handled by this server. That is useful when-to-use and when-not-to-use guidance, though it does not point to a specific sibling alternative.

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