Skip to main content
Glama

Brainy Prices — UAE Cost of Living

mobile_internet_plans

Read-onlyIdempotent

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

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": "mobile_internet_plans"
  }
}

Input Schema

NameRequiredDescriptionDefault
sortNoprice_aed_per_month
typeNo
cursorNo
statusNo
max_aedNo
plan_idNo
operatorNo
page_sizeNo
min_data_gbNo

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. Changed15 schema fields changed
    • 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"
      +  }
      +]
  4. Added

TDQS

C2.2/5.0
Behavior2/5

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

Annotations already declare this as a safe read-only, idempotent, non-destructive, closed-world operation. The description adds only content attributes (VAT-inclusive price, data, contract) and says nothing about pagination, filtering, sorting behavior, status semantics, or what the tool actually returns beyond the output schema.

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 very short and front-loads the domain, but it is a fragment rather than a structured tool description. It avoids waste, yet under-specification makes the structure feel incomplete rather than efficient.

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 explained, and annotations cover safety. However, for a nine-parameter paginated catalog with three enums and no schema descriptions, the description is far too thin to help an agent invoke it correctly.

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

Parameters1/5

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

Schema description coverage is 0% and the tool has nine parameters, including sort, type, cursor, status, max_aed, plan_id, operator, page_size, and min_data_gb. The description does not explain any parameter or how the price/data/contract fields relate to filtering, sorting, or pagination.

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 ('UAE mobile and home internet plans') and highlights fields (VAT-inclusive price, data, contract), but it provides no verb such as list, search, or compare. An agent can infer it is a catalog tool, but the intended action remains vague.

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 versus alternatives, nor any mention of prerequisites, exclusions, or intended query patterns. The domain is unique among siblings, but that is left implicit rather than stated.

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