Skip to main content
Glama

Check if a power bank can fly

check_power_bank_flight
Read-onlyIdempotent

Says whether a verified power bank can go in carry-on luggage, based only on the Wh rating the brand states (under 100Wh: no airline approval needed). Recalled models always return "recalled, do not fly". Includes the rule used and the product source.

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": {
      "product": "<product>"
    },
    "name": "check_power_bank_flight"
  }
}

Input Schema

NameRequiredDescriptionDefault
langNoLanguage of text fields (notes, labels, answers). One of: "en" (English), "zh-hant" (Traditional Chinese), "zh-hans" (Simplified Chinese). Default "en". Spec values and model numbers are the same in every language. Example: "zh-hant".en
productYesRequired. The power bank to check: its slug, model number, another model number it is sold under, or words from its name (1 to 120 characters, case ignored). Products from other categories are rejected. Example: "A1695" or "Anker Prime 20K".

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / lang / description
      Previous value: -"Language for text fields: en, zh-hant (Traditional Chinese) or zh-hans (Simplified Chinese)."New value: +"Language of text fields (notes, labels, answers). One of: \"en\" (English), \"zh-hant\" (Traditional Chinese), \"zh-hans\" (Simplified Chinese). Default \"en\". Spec values and model numbers are the same in every language. Example: \"zh-hant\"."
    • changedInput schema / properties / product / description
      Previous value: -"Power bank slug, model number or name, for example \"A1340\"."New value: +"Required. The power bank to check: its slug, model number, another model number it is sold under, or words from its name (1 to 120 characters, case ignored). Products from other categories are rejected. Example: \"A1695\" or \"Anker Prime 20K\"."
  2. 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 this is a read-only, idempotent, non-destructive, closed-world check, so the safety bar is largely met structurally. The description adds real value by disclosing the decision rule (under 100Wh needs no airline approval) and the forced "recalled, do not fly" outcome. It is still silent on what happens for over-100Wh or unknown-Wh products, so the transparency is partial.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three short sentences with zero padding, and the core capability is front-loaded ahead of the rule caveat and the recalled exception. Every clause carries information an agent would otherwise have to guess.

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?

There is no output schema, so the description must describe returns, and it does so in outline (the rule used and the product source) while omitting the actual response shape or the failure text for rejected categories. For a two-parameter, single-verdict tool this is close to sufficient but not fully closed. A 4 would require stating what comes back for over-100Wh or non-power-bank inputs.

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%: both the 'product' slug/model/name input and the 'lang' enum are fully documented in the schema. The description's mention of the brand-stated Wh basis and product source adds storage/decision context but no new meaning about the parameters themselves. 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 opens with a concrete verb and resource: it "says whether a verified power bank can go in carry-on luggage." It also pins the decision basis to the brand-stated Wh rating, which separates it functionally from product-lookup siblings like get_product or search_products. It stops short of naming a sibling to route against, so a 4 rather than 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 Guidelines3/5

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

The scope limit ("based only on the Wh rating the brand states") and the recalled-model short circuit imply when the answer is trustworthy, but there is no explicit when-to-use/when-not-to-use guidance or pointer to an alternative tool. An agent must infer that it should resolve a product first via the lookup siblings. Adequate but leaves routing to inference.

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