Skip to main content
Glama

lodging-intelligence

by ro.tria
OverviewDiscussionsAdmin

Explore Areas

explore_areas
Read-onlyIdempotent

Clasează ZONE (nu cazări) după caracter, ca să răspunzi „unde să merg". scope: "judet" (implicit), "localitate" (în interiorul unui județ — dă where), "statiune" (litoral). Ranking după un semnal (sort) sau compozit (criterii). Dacă dai where, tool-ul rămâne în zona părinte rezolvată și nu întoarce județe naționale. Ex.: județele cele mai montane, localitățile cele mai verzi din Cluj, stațiunile cele mai potrivite pentru familie. Sursă: tria.ro.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sortNoO dimensiune de ranking: liniste, natura, verde, parcuri, arii_protejate, munte, schi, apa, family, gastro, vin_crame, crame, cultura_istorie, cultura, nightlife, business, relaxare, magnetism, turism, urbanitate, viata-de-seara, viata_de_seara (pentru statiune și plaja/farmec/anvergura/afluenta).
limitNoTop N (implicit 8, max 30)
scopeNoGranularitatea ariei: judet (implicit) | localitate | statiune
whereNoJudețul părinte pentru scope=localitate, ex. "Brașov"; acceptă și o localitate/stațiune, caz în care se folosește județul ei. Dacă `scope=judet` și dai `where`, tool-ul auto-corectează la localitățile din județul/locul rezolvat.
criteriiNoRanking compozit (media) — doar pentru statiune.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
areasNoZonele clasate
judetNoJudețul părinte (doar scope=localitate)
scopeNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • changedInput schema / properties / sort / description
      Previous value: -"O dimensiune de ranking: liniste, natura, verde, parcuri, arii_protejate, munte, schi, apa, family, gastro, vin_crame, crame, cultura_istorie, cultura, nightlife, business, relaxare, magnetism, turism, urbanitate (pentru statiune și plaja/farmec/anvergura/afluenta)."New value: +"O dimensiune de ranking: liniste, natura, verde, parcuri, arii_protejate, munte, schi, apa, family, gastro, vin_crame, crame, cultura_istorie, cultura, nightlife, business, relaxare, magnetism, turism, urbanitate, viata-de-seara, viata_de_seara (pentru statiune și plaja/farmec/anvergura/afluenta)."
    • addedOutput schema / properties / areas / items / properties / find_args
      Added value: +{
+  "description": "Argumente replayabile pentru find_accommodations. Folosește-le ca atare pentru follow-up pe cazare.",
+  "properties": {
+    "criterii": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "where": {
+      "type": "string"
+    }
+  },
+  "type": "object"
+}
    • addedOutput schema / properties / areas / items / properties / where
      Added value: +{
+  "description": "Valoarea exactă de folosit în find_accommodations(where) pentru zona asta",
+  "type": "string"
+}
  2. Changed2 schema fields changed
    • changedInput schema / properties / sort / description
      Previous value: -"O dimensiune de ranking: liniste, natura, munte, apa, family, gastro, vin_crame, crame, cultura_istorie, cultura, nightlife, business, relaxare, magnetism, turism, urbanitate (pentru statiune și plaja/farmec/anvergura/afluenta)."New value: +"O dimensiune de ranking: liniste, natura, verde, parcuri, arii_protejate, munte, schi, apa, family, gastro, vin_crame, crame, cultura_istorie, cultura, nightlife, business, relaxare, magnetism, turism, urbanitate (pentru statiune și plaja/farmec/anvergura/afluenta)."
    • changedInput schema / properties / where / description
      Previous value: -"Doar scope=localitate — județul părinte, ex. \"Brașov\"."New value: +"Județul părinte pentru scope=localitate, ex. \"Brașov\"; acceptă și o localitate/stațiune, caz în care se folosește județul ei. Dacă `scope=judet` și dai `where`, tool-ul auto-corectează la localitățile din județul/locul rezolvat."
  3. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is known. The description adds valuable behavioral details: when `where` is provided, the tool stays in the resolved parent area and does not return national counties, plus auto-correction behavior for `scope=judet`.

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

Conciseness5/5

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

The description is compact, front-loaded with the main purpose, and contains no wasted words. It packs in scope options, `where` behavior, examples, and data source in a single efficient paragraph.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The description covers all key behavioral aspects: scope granularity, use of `where` to constrain results, ranking via `sort` or `criterii`, and provides multiple examples that illustrate the tool's range. With an output schema present, return structure need not be explained.

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 parameters are already well-documented. The description adds example use cases and clarifies the `sort` vs `criterii` ranking modes, but these are largely redundant with the schema's own descriptions.

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

Purpose5/5

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

The verb 'Clasează' (ranks) with resource 'ZONE' and explicit exclusion 'nu cazări' clearly distinguishes from accommodation siblings. It identifies the tool's purpose as answering 'where to go' by area character, which is specific and unambiguous.

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

Usage Guidelines4/5

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

It gives clear context for when to use: ranking areas by character with scope options (judet, localitate, statiune) and illustrative examples (mountainous counties, green localities, family resorts). It implicitly excludes accommodation searches but does not explicitly name alternatives.

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

All lodging-intelligence toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources