Skip to main content
Glama

Asia Miles Calculator

Calculate Asia Miles & Mixed Cabin Redemption

calculate_asia_miles
Read-only

Calculate Asia Miles redemption plans for 1-segment direct or 2-segment connecting itineraries. Automatically returns Full Economy, Full Business, and proportional Mixed-Cabin (Business + Economy / Economy + Business) mileage options, savings vs Full Business, route validation, and direct vs via-HKG comparisons.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "segment1": "<segment1>"
    },
    "name": "calculate_asia_miles"
  }
}

Input Schema

NameRequiredDescriptionDefault
segment1Yes
segment2No

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, so the safety profile is covered. The description adds genuinely useful disclosure of what the response contains — full economy, full business, proportional mixed-cabin, savings vs full business, route validation, and direct vs via-HKG comparison — but says nothing about failure modes such as invalid/unserved routes beyond naming 'route validation'.

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?

Two dense sentences, front-loaded with the operation and scope, then the return payload. Every clause carries information; no filler or repetition of the title.

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 correctly carries the burden of describing return values and does so thoroughly. Given two nested-object parameters and a simple read-only calculation, the only real omission is cabinClass semantics.

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?

The phrase '1-segment direct or 2-segment connecting' conveys that segment2 is optional, which is real meaning beyond the schema. However, the description never mentions the cabinClass inputs or clarifies how they interact with the statement that all cabin plans are returned, leaving the most non-obvious parameter behavior unexplained.

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 ('Calculate Asia Miles redemption plans') plus the exact scope: 1-segment direct or 2-segment connecting itineraries. It is clearly distinct from the sibling route/airport lookup tools, though it never names them explicitly.

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?

The scope clause ('1-segment direct or 2-segment connecting') implicitly tells the agent when this tool applies, but there is no explicit when-not guidance and no named alternative for other mileage scenarios.

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.