Skip to main content
Glama

gva_layer_info

Retrieve metadata for GIS layers including fields, geometry types, spatial references, and extents to understand data structure and capabilities.

Instructions

Get metadata information about the GVA GIS layer (fields, geometry type, spatial reference, extent)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Python handler for the 'gva_layer_info' tool: fetches layer metadata from ArcGIS API using make_request and returns formatted JSON response.
    if name == "gva_layer_info":
        # Get layer metadata
        url = f"{BASE_URL}/{LAYER_ID}"
        params = {'f': 'json'}
        data = make_request(url, params)
    
        # Format response
        result = {
            "name": data.get("name"),
            "type": data.get("type"),
            "geometryType": data.get("geometryType"),
            "spatialReference": data.get("spatialReference"),
            "extent": data.get("extent"),
            "fields": data.get("fields", [])
        }
    
        return [TextContent(
            type="text",
            text=json.dumps(result, indent=2, ensure_ascii=False)
        )]
  • TypeScript handler for the 'gva_layer_info' tool: fetches layer metadata from ArcGIS API using makeRequest and returns formatted JSON response.
    case "gva_layer_info": {
      // Get layer metadata
      const url = `${BASE_URL}/${LAYER_ID}`;
      const params = { f: "json" };
      const data = await makeRequest(url, params);
    
      // Format response
      const result = {
        name: data.name,
        type: data.type,
        geometryType: data.geometryType,
        spatialReference: data.spatialReference,
        extent: data.extent,
        fields: data.fields || [],
      };
    
      return {
        content: [
          {
            type: "text",
            text: JSON.stringify(result, null, 2),
          },
        ],
      };
    }
  • Registration of the 'gva_layer_info' tool in Python MCP server, including empty input schema (no parameters required).
    Tool(
        name="gva_layer_info",
        description="Get metadata information about the GVA GIS layer (fields, geometry type, spatial reference, extent)",
        inputSchema={
            "type": "object",
            "properties": {},
            "required": []
        }
    ),
  • Registration of the 'gva_layer_info' tool in TypeScript MCP server, including empty input schema (no parameters required).
      name: "gva_layer_info",
      description: "Get metadata information about the GVA GIS layer (fields, geometry type, spatial reference, extent)",
      inputSchema: {
        type: "object",
        properties: {},
        required: [],
      },
    },
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 burden. It indicates a read operation ('Get metadata information'), which suggests non-destructive behavior, but does not disclose other traits such as authentication needs, rate limits, or response format. The description adds basic context but lacks detailed behavioral disclosure.

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 a single, efficient sentence that front-loads the core purpose ('Get metadata information') and lists specific metadata types without waste. Every word contributes to understanding the tool's function, making it appropriately sized 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?

Given the tool's simplicity (0 parameters, no output schema), the description is adequate but could be more complete. It explains what metadata is retrieved but does not cover the return format or any error conditions. Without annotations or output schema, additional context on behavioral aspects would enhance completeness for this read-only tool.

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?

The tool has 0 parameters with 100% schema description coverage, so no parameter documentation is needed. The description appropriately does not discuss parameters, focusing instead on the tool's purpose. This meets the baseline for tools with no parameters, as it avoids unnecessary details.

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 verb 'Get' and the resource 'metadata information about the GVA GIS layer', specifying the exact types of information returned (fields, geometry type, spatial reference, extent). It distinguishes from siblings like gva_count, gva_export_geojson, and gva_query by focusing on metadata retrieval rather than counting, exporting, or querying data.

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 implies usage for obtaining layer metadata, but does not explicitly state when to use this tool versus alternatives like gva_query for data access or gva_export_geojson for exporting. No exclusions or prerequisites are mentioned, leaving usage context inferred rather than clearly defined.

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/pepo1275/mcp4gva'

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