Skip to main content
Glama

wms_get_feature_info

Query feature information from a WMS layer at a WGS84 point, with optional buffer and info format parameters.

Instructions

Run WMS GetFeatureInfo at a WGS84 point against any WMS layer.

url/layer identify the service and layer (as for wms_add_layer). The query point is always given as WGS84 lat/lon - even for a WMS that's usually browsed in another CRS - since GetFeatureInfo's bbox axis order is CRS/version-dependent and this avoids that ambiguity; the request is sent with CRS=EPSG:4326, which is the coordinate system almost every public WMS supports as a fallback. buffer_deg is the half-width (in degrees) of the query window around the point - widen it if the target features are small relative to the layer's render resolution. info_format is usually "text/html", "text/plain", "application/json", or "application/vnd.ogc.gml" depending on what the server advertises (check ows_list_capabilities/the server's own docs).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
latYes
lonYes
urlYes
layerYes
buffer_degNo
info_formatNotext/html

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior3/5

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

No annotations present, so description carries full burden. Discloses CRS choice and buffer semantics. Does not mention read-only nature, error conditions, or authentication needs. Adequate but not fully transparent.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Description is detailed but each sentence adds value. Could be slightly more concise, but the information density is high and well-structured.

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?

Lacks description of output format/structure. No output schema provided, so the agent doesn't know what to expect from the tool response. Otherwise covers input and behavior well.

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

Parameters5/5

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

Schema coverage is 0%, but description adds rich meaning for all six parameters: explains coordinate system, buffer purpose, and info_format examples. Greatly enhances understanding beyond raw 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?

Clearly states the action (Run WMS GetFeatureInfo), resource (any WMS layer), and input (WGS84 point). Also references related tool wms_add_layer for contextual understanding, distinguishing it from siblings.

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?

Provides guidance on coordinate system handling (WGS84) and when to adjust buffer_deg. References ows_list_capabilities for info_format choices. Lacks explicit when-to-use vs siblings but the context is clear.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/piatkowski/qgis-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server