Lounge Frog

List a page's photos

list_images

Read-onlyIdempotent

Photos on an airport, terminal, or lounge page, best-voted first, with their credits.

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": {
      "subject": "<subject>",
      "ref": "<ref>"
    },
    "name": "list_images"
  }
}

Input Schema

Name	Required	Description	Default
`ref`	Yes	Slug or (for airports) IATA code
`subject`	Yes

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 declare readOnly, idempotent, non-destructive, and closed-world behavior, so the safety profile is covered. The description adds genuine value beyond that by disclosing the result ordering ('best-voted first') and that credits are included in the response. It does not mention pagination or result limits, which is the remaining gap.

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?

A single compact sentence with zero filler, front-loading the resource and scope before the ordering and return-content details. Nothing is redundant or misplaced.

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?

For a two-parameter, read-only listing tool with no output schema, the description covers what is returned (photos), how it is ordered (by votes), and that credits accompany each item. It leaves open whether results are paginated or capped, which is a minor but real omission for a list operation.

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 50%: 'ref' is documented as 'Slug or (for airports) IATA code' and 'subject' has an enum of airport/terminal/lounge. The description restates the same three page types but adds no format detail, such as how to form a slug or whether the ref must match the subject type. Baseline 3 is appropriate given the schema carries the parameter documentation.

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 names the resource (photos) and its scope (airport, terminal, or lounge pages), matching the 'list' verb in the tool name, so an agent knows exactly what it retrieves. It is clear but does not explicitly differentiate from any sibling, though none of the listed siblings appear to return images.

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 implied rather than stated: an agent can infer it should call this when it needs photos for a specific airport/terminal/lounge page. There is no explicit when-to-use, no prerequisites, and no mention of alternatives, but no obvious competing tool exists in the sibling list.

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?