Skip to main content
Glama

Nadveo — book air-conditioning service

by com.nadveo
OverviewDiscussionsAdmin

Find a company

find_companies
Read-only

Service companies in the Nadveo catalog, filtered by country (ISO code, e.g. AE), city, district, service and name, best first. Each has its districts (main: fast arrival; secondary: next day or a call-out fee), "from" prices, the next free day and clients' rating, and badges: online_booking, quote_hours (how long a quote request waits for its quote, on average over 90 days; null — too few yet), amc (runs annual maintenance contracts), portal (gives its clients a portal).

Input Schema

NameRequiredDescriptionDefault
cityNoThe city, e.g. Dubai, Abu Dhabi, Sharjah (part of the name is enough).
queryNoPart of the company name.
tradeNohvac = air conditioning and heating; repair = electrical, plumbing and other repairs. Matches the services a company offers, not only its main trade.
countryNoISO 3166 code, e.g. AE, MX, ID, TH, VN.
serviceNoOlder form of category for air conditioning: maintenance = hvac.maintenance, repair = hvac.repair, installation = hvac.installation.
categoryNoThe kind of service, e.g. hvac.maintenance, hvac.repair, repair.electrical, repair.plumbing.
districtNoThe client's district in that city, e.g. "JLT", "Dubai Marina", "Al Nahda" (part of the name is enough).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedInput schema / properties / category
      Added value: +{
+  "description": "The kind of service, e.g. hvac.maintenance, hvac.repair, repair.electrical, repair.plumbing.",
+  "enum": [
+    "hvac.maintenance",
+    "hvac.repair",
+    "hvac.installation",
+    "hvac.emergency",
+    "hvac.commercial",
+    "hvac.rental",
+    "hvac.other",
+    "repair.appliances",
+    "repair.electronics",
+    "repair.plumbing",
+    "repair.electrical",
+    "repair.handyman",
+    "repair.other",
+    "rental.equipment",
+    "rental.tools",
+    "rental.events",
+    "rental.other"
+  ],
+  "type": "string"
+}
    • changedInput schema / properties / service / description
      Previous value: -"maintenance = cleaning and service; repair = repairs and gas recharge; installation."New value: +"Older form of category for air conditioning: maintenance = hvac.maintenance, repair = hvac.repair, installation = hvac.installation."
    • changedInput schema / properties / trade / description
      Previous value: -"hvac = air conditioning and heating."New value: +"hvac = air conditioning and heating; repair = electrical, plumbing and other repairs. Matches the services a company offers, not only its main trade."
  2. Changed3 schema fields changed
    • changedInput schema / properties / city / description
      Previous value: -"Part of the city name."New value: +"The city, e.g. Dubai, Abu Dhabi, Sharjah (part of the name is enough)."
    • addedInput schema / properties / district
      Added value: +{
+  "description": "The client's district in that city, e.g. \"JLT\", \"Dubai Marina\", \"Al Nahda\" (part of the name is enough).",
+  "type": "string"
+}
    • addedInput schema / properties / service
      Added value: +{
+  "description": "maintenance = cleaning and service; repair = repairs and gas recharge; installation.",
+  "enum": [
+    "maintenance",
+    "repair",
+    "installation"
+  ],
+  "type": "string"
+}
  3. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint=false. The description adds substantial context beyond that: it explains returned attributes such as districts, from-prices, next free day, ratings, and the meaning of badges like quote_hours and amc. It does not mention pagination, result limits, or how 'best first' is computed.

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?

The description is dense but front-loads the core purpose and resource. The badge definitions are long but earn their place because no output schema exists. The single long sentence could be split for readability, but there is no wasted filler.

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 no output schema, the description carries the burden of explaining return values, and it does so thoroughly by naming districts, prices, availability, ratings, and badges. It lacks pagination or limit details, but the schema also has no such parameters, so the remaining gaps are minor.

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

Parameters3/5

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

Schema description coverage is 100%, so all seven parameters are already documented in the schema. The description reinforces the country filter with an ISO example but adds no parameter-specific meaning beyond what the schema provides, making 3 the correct baseline.

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?

The description clearly states a specific verb and resource: service companies in the Nadveo catalog, filtered by several attributes and returned best-first. It does not explicitly distinguish itself from the sibling company_info tool, so it misses the top mark.

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

Usage Guidelines3/5

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

Usage is implied by the list of filters and the phrase 'filtered by', but the description never states when to choose this search tool over company_info or list_services. An agent can infer it is for discovery, but explicit routing guidance is absent.

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

All Nadveo — book air-conditioning service toolsInspect
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