Skip to main content
Glama

cost_of_living_overview

Read-onlyIdempotent

Compare Dubai cost-of-living ranges for rent, utilities, groceries, transport, and schooling, and view sample monthly budgets for singles, couples, and families.

Instructions

Headline cost-of-living ranges across rent, utilities, groceries, transport, and schooling, plus a sample monthly budget for a single person, a couple, and a family of four.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

A3.6/5.0
Behavior4/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 settled. The description adds useful content context by disclosing the exact shape of the output (ranges per category plus three household budget samples), which goes beyond what annotations convey.

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 front-loaded sentence with no filler; the enumeration of categories and the sample-budget addendum each carry information. It is efficient and appropriately sized for a no-argument informational tool.

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?

With zero parameters, annotations covering the safety profile, and an output schema present, the description only needs to convey what the tool provides, which it does clearly. The one gap is the absence of routing guidance against the many component estimators.

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

Parameters4/5

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

The tool takes zero parameters, so per the rubric the baseline is 4. There are no parameter semantics to describe and none are missing.

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

Purpose4/5

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

States a specific resource (cost-of-living ranges) and enumerates the covered categories (rent, utilities, groceries, transport, schooling) plus sample monthly budgets. It is unambiguous what the tool returns, though it never explicitly distinguishes itself from the granular sibling estimators like rent_estimate or grocery_estimate.

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?

No when-to-use guidance and no alternatives named, despite numerous related siblings (rent_estimate, dewa_bill_estimate, grocery_estimate, school_fee_estimate). An agent must infer that this is the aggregated overview versus the per-item estimators.

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

Deploy Server

Other Tools