Lounge Frog

Airport and terminal amenity metrics

get_amenity_metrics

Read-onlyIdempotent

The metric slugs an airport or a terminal is scored on (1-5: security speed, baggage delivery, ...) with what a 5 means, and the page explaining how Lounge Frog rates them.

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": "get_amenity_metrics"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 5, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already establish read-only, idempotent, closed-world behavior. The description adds useful behavioral context by saying the response contains metric slugs, score meanings, and a ratings explainer page, though it does not state auth needs or response structure.

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 sentence with no filler, though its nested clause structure ('with what a 5 means, and the page...') is slightly dense. The core purpose is still front-loaded.

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

Completeness4/5

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

No output schema exists, so the description must describe the return content; it identifies the key pieces: slugs, score definitions, and the explainer page. For a zero-parameter reference tool this is adequate, though it could specify whether the result is a list or a single object.

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

Parameters4/5

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

Zero parameters means the schema imposes no semantic burden, so the baseline is 4. The description adds no parameter meaning because there are none.

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 identifies the resource as airport/terminal amenity metric definitions and lists the returned components: metric slugs, 1-5 scoring examples, what a 5 means, and a rating explainer page. It is clear but does not explicitly distinguish from metric-definition siblings like get_airline_metrics or get_lounge_metrics.

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?

No explicit when-to-use, when-not-to-use, or sibling alternative is named. An agent can infer this is a reference lookup for scoring criteria, but the routing guidance is only implied.

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

All Lounge Frog tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?