Skip to content
Eden Engine
Get started

NC OneMap ArcGIS Service Directory

nconemap/list-services

Lists what the NC OneMap ArcGIS REST server publishes: its folders and the services at the root, each with its type (MapServer, FeatureServer, ImageServer, GPServer). Folders include AddressNC, Broadband, Elevation, Imagery and Utilities; root services include NC1Map_Parcels, NC1Map_Boundaries and NC1Map_Hydrography. Takes no input and returns the directory as the server sends it. Passed through unmodified and served by Omnial.

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

NC OneMap (NC Center for Geographic Information and Analysis)

Data from NC OneMap, North Carolina Center for Geographic Information and Analysis (NCCGIA) and the contributing North Carolina county governments. Passed through unmodified and served by Omnial; not an official NC OneMap 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: "nconemap/list-services" })

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

// 4. run: price the exact call first, then run it
omnial_execute({ tool: "nconemap/list-services", input: { /* see input_schema */ }, dry_run: true })
omnial_execute({ tool: "nconemap/list-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 21, 2026

Input and output schemas

Input schema
input_schema.json
{
  "type": "object",
  "properties": {},
  "additionalProperties": false
}
Output schema
output_schema.json
{
  "type": "object",
  "required": [
    "currentVersion"
  ],
  "properties": {
    "folders": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "description": "Folder names that group further services."
    },
    "services": {
      "type": "array",
      "items": {
        "type": "object",
        "properties": {
          "name": {
            "type": "string"
          },
          "type": {
            "type": "string",
            "description": "MapServer, FeatureServer, ImageServer, GPServer and so on."
          }
        },
        "additionalProperties": true
      },
      "description": "Services at the root of the directory."
    },
    "currentVersion": {
      "type": "number",
      "description": "ArcGIS Server version."
    }
  },
  "description": "The ArcGIS REST root directory: `folders` lists the service folders and `services` lists the services published at the root, each with its `name` and `type`.",
  "additionalProperties": true
}