Skip to main content
Glama
@climeqai/mcp-server

@climeqai/mcp-server

Official
by climeqai

climeq_calculate_air_travel

Calculate Scope 3.6 business flight emissions from IATA origin and destination codes, including cabin class multipliers and optional ISO 14083 radiative forcing disclosure.

Instructions

Calculate Scope 3.6 business flight emissions from IATA airport codes with cabin class multipliers and separate ISO 14083 Radiative Forcing disclosure.

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": {
      "origin": "<origin>",
      "destination": "<destination>"
    },
    "name": "climeq_calculate_air_travel"
  }
}

Input Schema

NameRequiredDescriptionDefault
originYesOrigin IATA airport code (e.g., 'IST', 'LHR').
persistNo
roundTripNo
cabinClassNoeconomy
passengersNo
destinationYesDestination IATA airport code (e.g., 'FRA', 'JFK').
includeRadiativeForcingNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.2.0

TDQS

A3.6/5.0
Behavior3/5

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

The description adds genuine methodology context beyond annotations: cabin class multipliers and a separately disclosed ISO 14083 Radiative Forcing figure. However, annotations declare readOnlyHint=false and idempotentHint=false, implying a write side effect, yet the description never explains what the 'persist' parameter writes, whether recalculation duplicates records, or what the response contains.

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?

A single front-loaded sentence with no filler, covering inputs, method, and disclosure. It is dense with domain jargon (Scope 3.6, ISO 14083) which is efficient for an informed agent but slightly reduces immediate readability.

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

Completeness3/5

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

For a 7-parameter tool with 29% schema coverage, no output schema, and a non-read-only annotation profile, the description leaves notable gaps: return value shape and units, persistence behavior, and the round-trip and passenger-count defaults. It covers the calculation's core concept adequately but not enough for confident invocation on the write path.

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 coverage is only 29%, with origin/destination documented and cabinClass enum self-explanatory, but roundTrip (defaulting to true), passengers, and persist are undocumented anywhere. The description partially compensates by explaining that cabin class affects the multiplier and that RF is a separate disclosure tied to includeRadiativeForcing, but three parameters remain semantically opaque.

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?

States a specific verb (Calculate) and a precise resource (Scope 3.6 business flight emissions) with the input modality (IATA airport codes). This is clearly distinguishable from sibling calculators such as commuting, electricity, fuel, or intermodal freight without opening any schema.

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 only implied: the agent can infer this is the tool for business air travel. There is no explicit when-to-use framing, no note that it is the wrong tool for freight or ground transport, and no mention of prerequisites such as valid IATA codes or supported regions.

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