GIS MCP Server

Overview Schema Source Related Servers Discussions Admin

metadata_raster

Open a raster dataset in read-only mode and retrieve its metadata. Accepts a local file path or HTTPS URL for quick inspection of geospatial raster properties.

Instructions

Open a raster dataset in read-only mode and return metadata.

This tool supports two modes based on the provided string:

A local filesystem path (e.g., "D:\Data\my_raster.tif").
An HTTPS URL (e.g., "https://example.com/my_raster.tif").

The input must be a single string that is either a valid file path on the local machine or a valid HTTPS URL pointing to a raster.

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": {
      "path_or_url": "<path_or_url>"
    },
    "name": "metadata_raster"
  }
}

Input Schema

Name	Required	Description	Default
`path_or_url`	Yes

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedv1.0.0Jan 2, 2026

removedInput schema / properties / path_or_url / title
```
Removed value: -"Path Or Url"
```

removedInput schema / title

Removed value: -"metadata_rasterArguments"

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "type": "object"
+}

First observedAug 19, 2025

TDQS

A4.2/5.0

Behavior4/5

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

The description discloses read-only behavior and the supported input types (local path and HTTPS URL). While no annotations are provided, the description adequately communicates the tool's non-destructive nature. The presence of an output schema reduces the need to detail return values.

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 concise with only a few sentences, front-loading the key purpose and then clarifying input modes. No unnecessary information, and the structure is easy to scan.

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?

Given the tool's simplicity (one parameter, output schema exists), the description covers the essential context: read-only mode, supported inputs, and the purpose. It is complete enough for an agent to select and invoke the tool, though it omits error handling or file format constraints.

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

Parameters4/5

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

Schema coverage for 'path_or_url' is 0%, but the description compensates by explaining that it is a file path or HTTPS URL, with examples. This adds significant semantic meaning beyond the bare schema.

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 opens a raster dataset in read-only mode and returns metadata. It specifies two modes (local file path and HTTPS URL) and distinguishes itself from sibling tools like get_raster_crs or raster_band_statistics by being a general metadata retrieval tool.

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 description provides context for when to use the tool (to get metadata from a raster), but does not explicitly exclude alternatives or advise against misuse. No mention of when to use this over more specific metadata tools such as get_raster_crs or raster_histogram.

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

Deploy Server