Skip to main content
Glama

LazyAnalysis — AI Solution Composer

Discover geospatial G1–G8 workflows

get_geospatial_capabilities
Read-onlyIdempotent

Read G1–G8 geospatial data contracts, native node availability, WGS84/CRS requirements, raster modes, G7 indexing and G8 Nx7 OGR vector topology. Specify workflow='coastal_raster', 'tiled_raster', 'indexed_features', or 'vector_gis' for known input/output pin links and configuration. Results are gated by this server's loaded native catalog; unsupported workflows are not represented as runnable. Does not execute the graph.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_geospatial_capabilities"
  }
}

Input Schema

NameRequiredDescriptionDefault
workflowNo
include_unavailableNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already establish read-only, idempotent, non-destructive, and closed-world behavior. The description adds useful behavioral context beyond annotations: results depend on the loaded native catalog, unsupported workflows are not shown as runnable, and the tool does not execute the graph. It does not explain include_unavailable behavior, but the annotation coverage lowers the burden.

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?

The definition is front-loaded and compact: it starts with the read action, then gives workflow values, then states gating and non-execution. The dense technical enumerations (G7 indexing, G8 Nx7 OGR topology) are relevant but could be hard to parse quickly. It contains no obvious filler.

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?

For a read-only capability-discovery tool with no output schema, the description adequately states scope, catalog gating, and non-execution. The main completeness gap is the unexplained include_unavailable parameter and what happens when workflow is omitted. Those gaps are notable but not fatal given the tool's simple read-only nature and strong annotations.

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 0%, so the description must carry parameter meaning. It explains the workflow values and their purpose for pin links and configuration, but it does not explain the include_unavailable parameter or the behavior of an empty/default workflow. Coverage is therefore partial for a two-parameter tool.

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 uses a specific verb, 'Read', and a specific resource, 'G1–G8 geospatial data contracts', then enumerates what is covered: native node availability, CRS requirements, raster modes, indexing, and OGR topology. The geospatial qualifier and the explicit 'Does not execute the graph' boundary make the tool's purpose clear.

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 gives clear context for specifying workflow='coastal_raster', 'tiled_raster', 'indexed_features', or 'vector_gis' to obtain input/output pin links and configuration. It also clarifies that results are catalog-gated and unsupported workflows are not runnable. However, it does not explicitly name an alternative tool or state when to omit workflow/include_unavailable.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources