Skip to main content
Glama

Brainy Prices — UAE Cost of Living

data_sources

Read-onlyIdempotent

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

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "data_sources"
  }
}

Input Schema

NameRequiredDescriptionDefault
cursorNo
statusNo
page_sizeNo
source_idNo
dataset_idNo
license_statusNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • removedOutput schema / $schema
      Removed value: -"https://json-schema.org/draft/2020-12/schema"
  2. Changed1 schema field changed
    • removedInput schema / $schema
      Removed value: -"https://json-schema.org/draft/2020-12/schema"
  3. Changed6 schema fields changed
    • 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"
      +  }
      +]
  4. Added

TDQS

C2.6/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 covered. The description adds some useful context by noting publishers, licences, dates, and paused sources, but it does not explain pagination, filtering behavior, ordering, or what 'paused' means in results.

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

Conciseness3/5

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

The description is compact and has no filler, so it is concise. However, the fragmentary phrasing is under-specified for a six-parameter tool and does not front-load an actionable statement of what the tool does.

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 and annotations are present, so return shape and safety are partly covered. Still, for a six-filter provenance endpoint, the description omits how filters combine, what the status and license_status enums mean operationally, and when an agent should call this tool rather than another.

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?

There are six parameters with 0% schema description coverage, and the description never names or explains cursor, page_size, source_id, dataset_id, status, or license_status. The words 'licences' and 'paused sources' loosely hint at two filter concepts, but no explicit parameter meaning or syntax is supplied.

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 indicates provenance metadata ('where each number comes from') and enumerates attributes such as publishers, licences, dates, and paused sources, so the general topic is inferable. However, it omits a clear verb/resource action like 'list data sources' or 'get source metadata' and does not distinguish this tool from its many sibling data tools.

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 guidance on when to use this tool, when not to use it, or which sibling tools are alternatives. The agent must infer that this is for provenance lookups rather than cost, housing, grocery, or other domain data.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources