GIS MCP Server

Overview Schema Source Related Servers Discussions Admin

raster_histogram

Compute histogram of pixel values for each band in a raster dataset, with adjustable bin count for detailed distribution analysis.

Instructions

Compute histogram of pixel values for each band.

Parameters:

source: path to input raster.
bins: number of histogram bins.

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": {
      "source": "<source>"
    },
    "name": "raster_histogram"
  }
}

Input Schema

Name	Required	Description	Default
`source`	Yes
`bins`	No

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedv1.0.0Jan 2, 2026
- removedInput schema / properties / bins / title
```
Removed value: -"Bins"
```
- removedInput schema / properties / source / title
```
Removed value: -"Source"
```
- removedInput schema / title
```
Removed value: -"raster_histogramArguments"
```
- changedOutput schema / (root)
```
Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "type": "object"
+}
```
First observedAug 19, 2025

TDQS

B3.3/5.0

Behavior2/5

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

No annotations provided, so the description must convey behavioral traits. It only states 'compute histogram' without disclosing side effects, permissions, or whether it is read-only. No mention of return format or storage.

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?

Extremely concise: one sentence for purpose and brief parameter list. No unnecessary words or redundancy.

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?

Given the existence of an output schema (not shown), the description suffices for a simple tool with two parameters. However, lacks details on supported file formats or behavior when bands vary, which could help in context with many sibling tools.

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 has 0% description coverage; the description adds meaning for both parameters: 'source' is path to input raster and 'bins' is number of bins. However, it does not explain expected input formats or constraints beyond the schema types.

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 it computes histogram of pixel values for each band, using specific verbs and resource. It distinguishes from sibling raster tools like raster_band_statistics by focusing on histogram specifically.

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

Usage Guidelines2/5

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

No guidance on when to use this tool versus alternatives like raster_band_statistics or zonal_statistics. Does not mention prerequisites or context where histogram computation is preferred.

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

Deploy Server