Skip to main content
Glama
@climeqai/mcp-server

@climeqai/mcp-server

Official
by climeqai

climeq_calculate_intermodal_freight

Calculate ISO 14083/GLEC v3.2 emissions for multimodal freight across road, sea, air, and rail legs, transshipment hubs, and refrigerated cargo.

Instructions

Calculate ISO 14083 / GLEC v3.2 multimodal freight emissions across Road, Sea, Air, and Rail legs, transshipment hubs, and refrigerated cargo.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "climeq_calculate_intermodal_freight"
  }
}

Input Schema

NameRequiredDescriptionDefault
hubsNo
legsNo
persistNo
originCityNo
originCountryNo
transportModeNoAuto
isRefrigeratedNo
cargoWeightTonsNo
destinationCityNo
supplyChainStageNoUpstream
destinationCountryNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.2.0

TDQS

C2.8/5.0
Behavior2/5

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

Annotations already declare this is not read-only, not idempotent, and open-world; the description adds no behavioral context such as why it mutates (the persist flag), whether results are stored, network/API dependencies, or failure modes. For a non-idempotent, open-world calculation, the side-effect profile is left entirely undisclosed.

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; the standard reference and scope items are packed efficiently. It is concise almost to a fault, since brevity here costs coverage.

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 an 11-parameter, zero-annotation-explanation, no-output-schema calculation tool, the description covers the conceptual scope but not the mechanics an agent needs. The gap is real but partly offset by the recognizable ISO 14083 domain and the named modes.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% across 11 parameters, so the description must compensate and does not. It implies the transportMode enum values and the existence of hubs/legs/refrigeration, but explains nothing about the legs and hubs object shapes, how origin/destination interact with legs, units for cargoWeightTons, the meaning of supplyChainStage, or what persist actually does.

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 ... multimodal freight emissions') and pins the methodology (ISO 14083 / GLEC v3.2) plus the covered modes and features (hubs, transshipment, refrigerated cargo). It is distinguishable from siblings by its multimodal freight scope, though it never names a sibling such as climeq_calculate_air_travel to draw the boundary.

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

Usage Guidelines2/5

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

No when-to-use or when-not-to-use guidance, no prerequisites, and no routing to alternatives. An agent learns nothing about when to supply discrete legs plus hubs versus just origin/destination and transportMode.

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