Skip to main content
Glama

business_travel_flight_calculator

Read-onlyIdempotent

[Aviation business travel carbon & radiative forcing calculator. Deterministic calculation, read-only, side-effect free]. Audits Scope 3 Category 6 business flights with ICAO/DEFRA distance tiers and seating class allocations, including high-altitude non-CO2 radiative forcing multipliers. Usage: Use this tool to compute corporate air travel emissions for sustainability accounting and travel policy audits. Returns: JSON object with { flightDistanceKm: number, distanceBand: string, cabinClass: string, passengersCount: number, emissionFactorsGco2ePerPassengerKm: object, calculatedTotals: object }.

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": {
      "flightDistanceKm": "<flightDistanceKm>"
    },
    "name": "business_travel_flight_calculator"
  }
}

Input Schema

NameRequiredDescriptionDefault
cabinClassNoFlight seating class (default: ECONOMY)
numberOfFlightsNoNumber of flight legs or return trips (default: 1)
flightDistanceKmYesTotal one-way or round-trip flight distance in kilometres
numberOfPassengersNoNumber of passengers travelling (default: 1)
includeRadiativeForcingRfNoWhether to include the ~1.9x radiative forcing multiplier for aviation non-CO2 climate impacts (default: true)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and idempotentHint=true, so 'deterministic calculation, read-only, side-effect free' largely restates structured data rather than adding to it. The genuinely additive content is the methodology disclosure (distance tiers, cabin allocations, the high-altitude non-CO2 multiplier) and the return shape, but nothing is said about input validation, out-of-range distances, or limits on passenger/flight counts.

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 structure is strong: a bracketed tagline, then explicit 'Usage:' and 'Returns:' lines, with the core scope stated first. A small amount of space is spent restating annotation-covered traits (read-only, side-effect free), but there is no filler sentence.

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?

Although there is no output schema, the description enumerates the returned JSON fields (flightDistanceKm, distanceBand, cabinClass, passengersCount, emission factors, calculatedTotals), and the single required parameter plus four optional ones are all documented in the schema. For a deterministic single-purpose calculator this is sufficient for an agent to call it correctly without further exploration.

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%, and the schema already documents cabinClass defaults/enum, passenger and flight counts, and the ~1.9x radiative forcing flag. The description echoes these concepts (seating class allocations, radiative forcing multipliers) without adding formulas, units, or interaction rules beyond the schema, so the baseline 3 applies.

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 names a specific verb and resource: it 'audits Scope 3 Category 6 business flights' and computes carbon plus radiative forcing, with named methodologies (ICAO/DEFRA distance tiers, cabin class allocations). This is far more specific than the bare name, but it never explicitly distinguishes itself from adjacent siblings such as defra_freight_logistics_calculator or scope3_spend_based_eeio_calculator, so it stops short of a 5.

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?

The 'Usage:' line gives a clear context — corporate air travel emissions for sustainability accounting and travel policy audits — which tells the agent when the tool applies. There is no explicit when-not guidance and no named alternative for freight or spend-based Scope 3 calculations, which keeps it out of 5 territory.

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.

Resources