Skip to main content
Glama

Spare Luggage Calculator

spare_luggage_calculator
Read-onlyIdempotent

Calculate spare checked-baggage kilos from the bundled snapshot. Match airline name or IATA and confirm fare/route. Invalid or negative packed weight is treated as zero.

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": {
      "airline": "<airline>"
    },
    "name": "spare_luggage_calculator"
  }
}

Input Schema

NameRequiredDescriptionDefault
airlineYes
packed_kgNo
fare_or_cabinNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior4/5

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

Annotations already establish read-only, idempotent, non-destructive, closed-world behavior. The description adds useful context beyond those annotations: the snapshot data source and the edge-case rule that invalid or negative packed weight is treated as zero.

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?

Three short sentences are front-loaded with the purpose and contain no wasted wording. 'Confirm fare/route' is the only vague phrase, but the overall structure is efficient.

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?

The output schema covers return values and the annotations cover safety, which reduces the description's burden. However, for a calculator with 0% schema coverage, the description leaves fare_or_cabin under-explained and does not describe what the bundled snapshot contains or how the calculation uses it.

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?

With 0% schema description coverage, the description must carry the meaning of all three parameters. It explains that airline accepts a name or IATA code and clarifies how packed_kg handles negative or invalid values, but fare_or_cabin is only vaguely covered by 'confirm fare/route' and its purpose remains unclear.

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 states a specific verb and resource: calculate spare checked-baggage kilos from a bundled snapshot. It is clearly a distinct calculator tool, though it does not reference any sibling or explicitly differentiate itself from them.

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?

'Match airline name or IATA and confirm fare/route' is parameter guidance rather than a statement of when this tool should be chosen. There is no explicit when-to-use guidance, no when-not-to-use guidance, and no mention of alternatives.

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