Skip to main content
Glama
Sign In

Arcgis Palmbeach

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Layer Info

layer_info
Read-onlyIdempotent

Get an ArcGIS Feature/Map Service layer's schema by url: fields (name + type), geometry type, total record count, and capabilities.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "url": "https://services.arcgisonline.com/arcgis/rest/services/PalmBeachCounty/FeatureServer/0"
    },
    "name": "layer_info"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesFeature/Map Service layer url, e.g. ".../FeatureServer/0".

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "url": "https://services.arcgisonline.com/arcgis/rest/services/PalmBeachCounty/FeatureServer/0"
+  }
+]
  2. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint=false, covering safety. The description adds meaningful behavioral context by specifying the exact outputs (fields, geometry type, record count, capabilities) and limiting scope to schema retrieval, which is consistent with annotations. No contradiction.

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, well-structured sentence that front-loads the action and resource, then lists the returned items. Every word contributes value without redundancy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given only one parameter, rich annotations, and no output schema, the description adequately covers return values (schema fields, geometry type, count, capabilities). It is complete for the tool's simplicity and leaves no critical gaps.

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 100% coverage for the single `url` parameter, clearly describing it as a Feature/Map Service layer URL. The description's 'by url' adds no new semantics beyond the schema, so baseline 3 is appropriate.

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 'Get' with a clear resource: 'an ArcGIS Feature/Map Service layer's schema'. It enumerates exactly what's returned (fields, geometry type, record count, capabilities), which distinguishes it from sibling tools like query_layer that likely retrieve data rather than metadata.

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 schema inspection but does not explicitly state when to use this tool versus alternatives like query_layer or search_within. There is no mention of exclusions or preferred context, so guidance is only implied by the tool's purpose.

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

All Arcgis Palmbeach toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources