Brainy Prices — UAE Cost of Living

data_sources

Read-onlyIdempotent

Where each number comes from: publishers, licences, dates, paused sources.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`cursor`	No
`status`	No
`page_size`	No
`source_id`	No
`dataset_id`	No
`license_status`	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"
```

Changed6 schema fields changedOct 6, 2026

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

removedOutput schema / $defs / SourceListResponse

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

removedOutput schema / $defs / SourceResponse

Removed value: -{
-  "additionalProperties": false,
-  "properties": {
-    "data": {
-      "$ref": "#/$defs/Source"
-    },
-    "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/SourceListResponse"
-  },
-  {
-    "$ref": "#/$defs/SourceResponse"
-  },
-  {
-    "$ref": "#/$defs/ToolFailure"
-  }
-]New value: +[
+  {
+    "additionalProperties": false,
+    "properties": {
+      "data": {
+        "items": {
+          "$ref": "#/$defs/Source"
+        },
+        "type": "array"
+      },
+      "links": {
+        "$ref": "#/$defs/Links"
+      },
+      "meta": {
+        "$ref": "#/$defs/ResponseMeta"
+      }
+    },
+    "required": [
+      "meta",
+      "data",
+      "links"
+    ],
+    "type": "object"
+  },
+  {
+    "additionalProperties": false,
+    "properties": {
+      "data": {
+        "$ref": "#/$defs/Source"
+      },
+      "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=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered. The description adds only that the payload includes publishers, licences, dates and paused sources; it does not disclose pagination behavior despite a cursor/page_size schema or explain what 'unreadable' means.

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?

One short, front-loaded sentence with no padding; the core content list comes first. It is efficient, though a sentence fragment rather than a complete statement of action.

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?

An output schema exists so return values need not be described, but with 6 undocumented parameters, no required fields, and no usage context, the definition is materially incomplete for an agent needing to decide when and how to call it.

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 6 parameters, so the description carries the full explanatory burden. Its phrases ('licences', 'paused sources') only loosely gesture at license_status and status, and it says nothing about cursor, page_size, source_id or dataset_id, leaving the highest-value parameters undocumented.

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 conveys the content of the resource (publishers, licences, dates, paused sources) and implicitly identifies it as a data-provenance tool, which distinguishes it from the numeric siblings like costs_by_area. However, it has no verb and reads as a fragment ('Where each number comes from'), so the agent must infer that this is a list/retrieve operation for source metadata rather than a data lookup.

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 explicit guidance on when to call this tool versus the numeric siblings, nor any stated prerequisite (e.g. 'use to check provenance or find paused/restricted sources before trusting a figure'). The mention of 'paused sources' is a content hint, not usage instruction.

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?