Skip to content
Eden Engine
Get started

PASDA Pennsylvania GIS Server: Services in a Folder

pasda/folder-services

Lists the services in one folder of the Pennsylvania Spatial Data Access (PASDA) ArcGIS server, for example the pasda folder with its county, city and agency map services such as pasda/AdamsCounty. Each entry has the service name and type; use the name with the service-layers tool. An unknown folder returns a validation error. Passed through unmodified and served by Eden Engine; not an official PASDA or Penn State product.

activeper callv1

Price

$0.0026 per call

You pay the price shown. If a call turns out to cost more than its quote, you pay the actual price, capped at twice the quote. No monthly minimum. Top-ups start at $0.50.

Data source

Pennsylvania Spatial Data Access (PASDA), Penn State

Data from Pennsylvania Spatial Data Access (PASDA), Penn State, and the original data provider of each layer named in the service's copyright text. Served by Eden Engine; not an official PASDA or Penn State product.

Use it

Five steps: search, inspect, learn, run, settle. No per-tool setup; your agent reaches this tool through the meta-tools it already has.

Connect once and your AI can find and run this tool, and any other it needs.

Install itCreate an account
agent
// 1. search: find the tool
omnial_search({ query: "what you need" })

// 2. inspect: price and input schema
omnial_inspect({ tool: "pasda/folder-services" })

// 3. learn: read the usage guide at runtime
omnial_learn({ tool: "pasda/folder-services" })

// 4. run: price the exact call first, then run it
omnial_execute({ tool: "pasda/folder-services", input: { /* see input_schema */ }, dry_run: true })
omnial_execute({ tool: "pasda/folder-services", input: { /* ... */ } })

// 5. settle: the call is charged when it finishes, nothing to do

Not connected yet? Point your MCP client at https://mcp.eden-engine.com/mcp, then copy a config for your client.

Pricing

Every charge this tool can incur.

ChargePrice
Per call
$0.0026
Updated
Oct 24, 2026

Input and output schemas

Input schema
input_schema.json
{
  "type": "object",
  "required": [
    "folder"
  ],
  "properties": {
    "folder": {
      "type": "string",
      "pattern": "^[A-Za-z0-9_]{1,64}$",
      "description": "A folder name from the root listing, for example pasda or Utilities. Case matters."
    }
  },
  "additionalProperties": false
}
Output schema
output_schema.json
{
  "type": "object",
  "required": [
    "services"
  ],
  "properties": {
    "folders": {
      "type": "array",
      "items": {
        "type": "string"
      }
    },
    "services": {
      "type": "array",
      "items": {
        "type": "object",
        "properties": {
          "name": {
            "type": "string"
          },
          "type": {
            "type": "string"
          }
        },
        "additionalProperties": true
      },
      "description": "Each service with `name` (folder/service) and `type` (MapServer, GPServer, ...)."
    },
    "currentVersion": {
      "type": "number"
    }
  },
  "additionalProperties": true
}