Brainy Prices — UAE Cost of Living

mobile_internet_plans

Read-onlyIdempotent

UAE mobile and home internet plans: VAT-inclusive price, data, contract.

Input Schema

TableJSON Schema

Name	Required	Default
`sort`	No	price_aed_per_month
`type`	No
`cursor`	No
`status`	No
`max_aed`	No
`plan_id`	No
`operator`	No
`page_size`	No
`min_data_gb`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 13, 2026
- removedInput schema / $schema
```
Removed value: -"https://json-schema.org/draft/2020-12/schema"
```

Changed15 schema fields changedOct 6, 2026

removedInput schema / properties / sort / type
```
Removed value: -"string"
```
removedInput schema / properties / status / type
```
Removed value: -"string"
```
removedInput schema / properties / type / type
```
Removed value: -"string"
```

removedOutput schema / $defs / Provenance

Removed value: -{
-  "additionalProperties": true,
-  "required": [
-    "source_id",
-    "license_id",
-    "source_url",
-    "observed_on",
-    "observed_at",
-    "published_on",
-    "published_at",
-    "retrieved_at",
-    "stale",
-    "status",
-    "paused_since",
-    "flags"
-  ],
-  "type": "object"
-}

removedOutput schema / $defs / TelecomPlan / properties / category / type
```
Removed value: -"string"
```
removedOutput schema / $defs / TelecomPlan / properties / price_basis / type
```
Removed value: -[
-  "string",
-  "null"
-]
```
removedOutput schema / $defs / TelecomPlan / properties / provenance / $ref
```
Removed value: -"#/$defs/Provenance"
```
addedOutput schema / $defs / TelecomPlan / properties / provenance / additionalProperties
```
Added value: +true
```

addedOutput schema / $defs / TelecomPlan / properties / provenance / required

Added value: +[
+  "source_id",
+  "license_id",
+  "source_url",
+  "observed_on",
+  "observed_at",
+  "published_on",
+  "published_at",
+  "retrieved_at",
+  "stale",
+  "status",
+  "paused_since",
+  "flags"
+]

addedOutput schema / $defs / TelecomPlan / properties / provenance / type
```
Added value: +"object"
```
removedOutput schema / $defs / TelecomPlan / properties / status / type
```
Removed value: -"string"
```

removedOutput schema / $defs / TelecomPlanListResponse

Removed value: -{
-  "additionalProperties": false,
-  "properties": {
-    "data": {
-      "items": {
-        "$ref": "#/$defs/TelecomPlan"
-      },
-      "type": "array"
-    },
-    "links": {
-      "$ref": "#/$defs/Links"
-    },
-    "meta": {
-      "$ref": "#/$defs/ResponseMeta"
-    }
-  },
-  "required": [
-    "meta",
-    "data",
-    "links"
-  ],
-  "type": "object"
-}

removedOutput schema / $defs / TelecomPlanResponse

Removed value: -{
-  "additionalProperties": false,
-  "properties": {
-    "data": {
-      "anyOf": [
-        {
-          "$ref": "#/$defs/TelecomPlan"
-        },
-        {
-          "type": "null"
-        }
-      ]
-    },
-    "links": {
-      "$ref": "#/$defs/Links"
-    },
-    "meta": {
-      "$ref": "#/$defs/ResponseMeta"
-    }
-  },
-  "required": [
-    "meta",
-    "data",
-    "links"
-  ],
-  "type": "object"
-}

removedOutput schema / $defs / ToolFailure

Removed value: -{
-  "additionalProperties": false,
-  "properties": {
-    "error": {
-      "additionalProperties": false,
-      "properties": {
-        "code": {
-          "type": "string"
-        },
-        "message": {
-          "type": "string"
-        },
-        "retry_after_s": {
-          "type": [
-            "integer",
-            "null"
-          ]
-        },
-        "retryable": {
-          "type": "boolean"
-        }
-      },
-      "required": [
-        "code",
-        "message",
-        "retryable",
-        "retry_after_s"
-      ],
-      "type": "object"
-    },
-    "request_id": {
-      "type": [
-        "string",
-        "null"
-      ]
-    }
-  },
-  "required": [
-    "error",
-    "request_id"
-  ],
-  "type": "object"
-}

changedOutput schema / anyOf

Previous value: -[
-  {
-    "$ref": "#/$defs/TelecomPlanListResponse"
-  },
-  {
-    "$ref": "#/$defs/TelecomPlanResponse"
-  },
-  {
-    "$ref": "#/$defs/ToolFailure"
-  }
-]New value: +[
+  {
+    "additionalProperties": false,
+    "properties": {
+      "data": {
+        "items": {
+          "$ref": "#/$defs/TelecomPlan"
+        },
+        "type": "array"
+      },
+      "links": {
+        "$ref": "#/$defs/Links"
+      },
+      "meta": {
+        "$ref": "#/$defs/ResponseMeta"
+      }
+    },
+    "required": [
+      "meta",
+      "data",
+      "links"
+    ],
+    "type": "object"
+  },
+  {
+    "additionalProperties": false,
+    "properties": {
+      "data": {
+        "anyOf": [
+          {
+            "$ref": "#/$defs/TelecomPlan"
+          },
+          {
+            "type": "null"
+          }
+        ]
+      },
+      "links": {
+        "$ref": "#/$defs/Links"
+      },
+      "meta": {
+        "$ref": "#/$defs/ResponseMeta"
+      }
+    },
+    "required": [
+      "meta",
+      "data",
+      "links"
+    ],
+    "type": "object"
+  },
+  {
+    "additionalProperties": false,
+    "properties": {
+      "error": {
+        "additionalProperties": false,
+        "properties": {
+          "code": {
+            "type": "string"
+          },
+          "message": {
+            "type": "string"
+          },
+          "retry_after_s": {
+            "type": [
+              "integer",
+              "null"
+            ]
+          },
+          "retryable": {
+            "type": "boolean"
+          }
+        },
+        "required": [
+          "code",
+          "message",
+          "retryable",
+          "retry_after_s"
+        ],
+        "type": "object"
+      },
+      "request_id": {
+        "type": [
+          "string",
+          "null"
+        ]
+      }
+    },
+    "required": [
+      "error",
+      "request_id"
+    ],
+    "type": "object"
+  }
+]

AddedOct 4, 2026

TDQS

C2.7/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is covered. The description adds one genuinely useful behavioral fact — prices are VAT-inclusive — but says nothing about pagination (a cursor parameter exists), result volume, or freshness/ranking semantics implied by the 'status' enum.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single compact sentence with the domain front-loaded and zero filler. It is appropriately sized in form, though the brevity comes at the cost of substance rather than being a model of efficiency.

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

Completeness2/5

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

With an output schema present, return values need not be explained, but nine undocumented parameters and cursor-based pagination go unmentioned. For a filtered, paginated listing tool, the description leaves an agent unable to construct a correct call without guessing at parameter intent.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% across nine parameters, so the description carries the full explanatory burden. It gestures at price and data, but gives no meaning for cursor, page_size, status (ranked/unverified/excluded), plan_id, operator, type, or the sort enum values — a significant gap when the schema documents nothing.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names the resource and its domain ('UAE mobile and home internet plans') and hints at returned fields (price, data, contract), but contains no verb — an agent cannot tell whether the tool lists, searches, or compares plans. The domain is distinct from all siblings, so sibling confusion is unlikely, but the action itself is only implied.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no statement of when to use this tool, when not to, or what alternatives exist. Sibling tools cover entirely different domains (rents, fuel, visas), so no routing conflict exists, but the agent gets no guidance on filtering intent (e.g., mobile vs home, budget vs data-driven search) despite nine filter parameters.

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

All Brainy Prices — UAE Cost of Living 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.

Resources

Need Help?