Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

agoda_flights_itinerary_amenities

Fetch Agoda flight segment amenities, including aircraft type, seat layout, meals, entertainment, and Wi-Fi, for one or more segments copied from a flight search response.

Instructions

Get Agoda flight segment amenities. Returns real-content amenities (aircraft type, seat layout, meals, entertainment, wifi) for one or more flight segments. Copy the segments straight from a flight search response's own segment fields.

Input Schema

NameRequiredDescriptionDefault
bodyYesOne or more flight segments to fetch amenities for

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.17.5
    • addedInput schema / properties / body / properties
      Added value: +{
+  "segments": {
+    "items": {
+      "properties": {
+        "cabin_class": {
+          "type": "string"
+        },
+        "carrier_code": {
+          "type": "string"
+        },
+        "departure_date_time": {
+          "type": "string"
+        },
+        "destination_airport": {
+          "type": "string"
+        },
+        "fare_basis_code": {
+          "type": "string"
+        },
+        "flight_number": {
+          "type": "string"
+        },
+        "origin_airport": {
+          "type": "string"
+        }
+      },
+      "required": [
+        "cabin_class",
+        "carrier_code",
+        "departure_date_time",
+        "destination_airport",
+        "flight_number",
+        "origin_airport"
+      ],
+      "type": "object"
+    },
+    "type": "array"
+  }
+}
    • addedInput schema / properties / body / required
      Added value: +[
+  "segments"
+]
  2. Added

TDQS

A3.9/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It discloses what is returned (a lookup of amenities) but says nothing about read-only safety, authentication needs, or failure modes. The input-sourcing hint adds some value but the safety/behavior profile is left implicit.

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?

Three short sentences, front-loaded with purpose, then return content, then input guidance. Every sentence earns its place with no repetition or 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?

For a lookup tool with no output schema, the description adequately explains what comes back and how to supply the nested segments. Remaining gaps (auth, error behavior, batching limits) are minor but non-trivial given zero annotation coverage.

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?

Schema coverage is 100% so the structured fields already document the segment shape. The description adds real value beyond the schema by explaining that the segment objects should be copied verbatim from a flight search response's own segment fields, clarifying the expected value source.

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 verb and resource ('Get Agoda flight segment amenities') and enumerates the return contents (aircraft type, seat layout, meals, entertainment, wifi). It implies its relationship to the flight search tool but never names agoda_flights_search as a sibling, so differentiation is by inference.

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?

Gives a concrete when/how instruction: 'Copy the segments straight from a flight search response's own segment fields,' which tells the agent where the input comes from and implies this is a follow-up call to a search. It does not state any exclusions or when not to use it.

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