Skip to main content
Glama

Airsockfly

Read FAQ

list_faq
Read-onlyIdempotent

Read Airsockfly frequently asked questions about booking, payments and cancellations.

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

Input Schema

NameRequiredDescriptionDefault
audienceNoFAQ group to read.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint=false, so the safety profile is covered by structured data. The description adds the topical scope of the content returned, but says nothing about response shape, whether the FAQ set is static, or how the two audience groups differ.

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?

One short sentence with no filler, front-loading the verb and resource and following with the content scope. Nothing redundant is present.

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 single-parameter read-only tool with annotations and full schema coverage, the description is adequate; no output schema exists, but the topical scope hints at what comes back. The only lingering gap is what the 'help' and 'home' FAQ groups actually contain, which the schema also leaves opaque.

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%, so the single optional 'audience' parameter is already documented in the schema. The description adds no meaning to the 'help' vs 'home' enum distinction, so it neither compensates nor detracts — baseline 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 names a concrete verb (Read) and resource (Airsockfly frequently asked questions) and scopes the content to booking, payments and cancellations. This is far more specific than a tautology like 'read FAQ', though it does not explicitly position itself against any sibling tool.

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 topic list (booking, payments, cancellations) implies the situations where this tool applies, but there is no explicit when-to-use or when-not-to-use statement and no named alternative. Usage is inferable rather than stated.

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