Opencellid

Cells In Area

cells_in_area

Read-onlyIdempotent

List cell towers inside a bounding box. Bounding box format: "lat_sw,lon_sw,lat_ne,lon_ne". OpenCellID caps results per call — narrow the bbox if you need detail.

Input Schema

Name	Required	Description
`mcc`	No	Restrict to a country (Mobile Country Code)
`mnc`	No	Restrict to a network within MCC
`bbox`	Yes	Bounding box "lat_sw,lon_sw,lat_ne,lon_ne"
`limit`	No	Max records (default 1000, server-capped)

Output Schema

Name	Required	Description
`bbox`	Yes	Bounding box used in query
`cells`	Yes	List of cell towers in area
`count`	Yes	Number of cell towers found

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedMay 22, 2026

addedInput schema / examples

Added value: +[
+  {
+    "bbox": "37.7749,-122.4194,37.8049,-122.3894"
+  },
+  {
+    "bbox": "37.7749,-122.4194,37.8049,-122.3894",
+    "limit": 500,
+    "mcc": 310,
+    "mnc": 410
+  }
+]

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "bbox": {
+      "description": "Bounding box used in query",
+      "type": "string"
+    },
+    "cells": {
+      "description": "List of cell towers in area",
+      "items": {
+        "properties": {
+          "avg_signal_strength": {
+            "description": "Average signal strength",
+            "type": [
+              "number",
+              "null"
+            ]
+          },
+          "cell_id": {
+            "description": "Cell ID",
+            "type": [
+              "number",
+              "null"
+            ]
+          },
+          "created_at": {
+            "description": "ISO 8601 timestamp of creation",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "lac": {
+            "description": "Location Area Code",
+            "type": [
+              "number",
+              "null"
+            ]
+          },
+          "latitude": {
+            "description": "Cell tower latitude",
+            "type": [
+              "number",
+              "null"
+            ]
+          },
+          "longitude": {
+            "description": "Cell tower longitude",
+            "type": [
+              "number",
+              "null"
+            ]
+          },
+          "mcc": {
+            "description": "Mobile Country Code",
+            "type": [
+              "number",
+              "null"
+            ]
+          },
+          "mnc": {
+            "description": "Mobile Network Code",
+            "type": [
+              "number",
+              "null"
+            ]
+          },
+          "radio": {
+            "description": "Radio type (GSM/UMTS/LTE/CDMA)",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "range_m": {
+            "description": "Cell tower coverage range in meters",
+            "type": [
+              "number",
+              "null"
+            ]
+          },
+          "samples": {
+            "description": "Number of samples collected",
+            "type": [
+              "number",
+              "null"
+            ]
+          },
+          "updated_at": {
+            "description": "ISO 8601 timestamp of last update",
+            "type": [
+              "string",
+              "null"
+            ]
+          }
+        },
+        "required": [
+          "mcc",
+          "mnc",
+          "lac",
+          "cell_id",
+          "radio",
+          "latitude",
+          "longitude",
+          "range_m",
+          "samples",
+          "avg_signal_strength",
+          "created_at",
+          "updated_at"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "count": {
+      "description": "Number of cell towers found",
+      "type": "number"
+    }
+  },
+  "required": [
+    "bbox",
+    "count",
+    "cells"
+  ],
+  "type": "object"
+}

First observedMay 13, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint. The description adds that results are capped by OpenCellID, a behavioral trait not covered by annotations. No contradictions.

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?

Two sentences that front-load the purpose and format, then add a critical limitation. No unnecessary words—every sentence adds value.

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?

Given the presence of an output schema, the description sufficiently explains the tool's operation and limitations. Could mention pagination or response structure, but not required.

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 coverage is 100%, so the schema already describes all parameters. The description reiterates the bbox format and adds context on caps, but does not significantly enhance parameter understanding beyond the schema.

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 'List' and resource 'cell towers' with a bounding box. It distinguishes from sibling tools like 'get_cell' which retrieves a single cell, and other unrelated tools.

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?

Provides guidance on narrowing the bounding box due to server-side caps, but does not explicitly state when to use versus alternatives like 'get_cell'. The context about caps is helpful for effective use.

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

All Opencellid tools Inspect

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.