Skip to main content
Glama

get_page_faqs

The FAQs shown on one site page, holiday, resort or ski test, in page order, with answers in Markdown. Give exactly one of path, holiday, resort or ski_test. For a holiday, add its resorts' slugs in with_resorts to include their FAQs too (as the holiday page does).

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_page_faqs"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathNoSite path, e.g. '/travel/etias/'
resortNoResort slug, e.g. from find_resort
holidayNoHoliday product key (attrs.product_key / `product_key` from search), e.g. 'alagna freeride'
ski_testNoSki test slug
with_resortsNoHoliday only: resort slugs whose FAQs to include

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It does disclose useful behavior: results come in page order, answers are Markdown, and with_resorts mirrors what the holiday page itself renders. It omits what happens when zero or multiple selectors are supplied, whether output is paginated, or any size limits.

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, front-loaded with what is returned, then the selector constraint, then the holiday edge case. No redundant restatement of parameter names beyond what is needed to state the constraint.

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 read-only retrieval tool with five optional parameters and no output schema, the description covers the critical risk (which selector to pass) and the return shape (ordered FAQs with Markdown answers). It could still say what an empty or invalid selector yields, but the essentials for correct invocation are present.

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?

Schema coverage is 100% so the baseline is 3, but the description adds meaning the schema cannot express: the mutual exclusivity of the four selectors (the schema has no oneOf/allOf enforcing this) and the fact that with_resorts only applies to holidays and takes resort slugs. That is genuine constraint information beyond the property descriptions.

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 exact resource returned (the FAQs shown on one page/holiday/resort/ski test) and its scope (page order, Markdown answers), which is specific enough to distinguish it from a single-FAQ tool like get_faq. It lacks an explicit verb but the retrieval intent is unambiguous.

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

Usage Guidelines4/5

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

It gives clear selection rules among the four selector parameters ('Give exactly one of `path`, `holiday`, `resort` or `ski_test`') and an additive rule for the holiday case. It does not state when to prefer this over sibling lookup tools such as get_faq, so it stops short of full alternative routing.

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