Skip to main content
Glama

Airsockfly

Open support case

create_support_case

Open a support case with Airsockfly customer service about a booking or another issue.

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": {
      "vertical": "<vertical>",
      "category": "<category>",
      "subject": "<subject>",
      "message": "<message>"
    },
    "name": "create_support_case"
  }
}

Input Schema

NameRequiredDescriptionDefault
messageYesDescription of the issue, at least 10 characters.
subjectYesShort subject of the case.
categoryYesWhat the case is about.
verticalYesService type.
bookingRefNoOrder or booking number the case is about.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, idempotentHint=false and openWorldHint=false, so the safety profile is covered. The description adds nothing beyond that – notably it does not warn that idempotentHint=false means repeated calls will create duplicate cases, nor does it say what happens after submission or whether a case reference is returned.

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 well-formed sentence that front-loads the action and resource with zero filler. Nothing extraneous and nothing buried.

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?

With four required parameters, two enums, and no output schema, an agent would benefit from knowing whether a case identifier is returned and how to handle a booking that spans multiple verticals. Those gaps are modest but real; the description covers the what but not the after-the-call consequences.

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 every parameter including the two enums is already documented in the schema, and the baseline is 3. The phrase "about a booking" loosely signals that bookingRef relates to the subject of the case, but the description adds no formatting, conditional-requirement, or enum-selection guidance beyond the schema.

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 gives a specific verb+resource ("Open a support case") plus the counterparty (Airsockfly customer service) and the subject matter (a booking or another issue), which clearly separates it from list_support_cases. It stops short of naming a sibling or clarifying how it differs from, say, cancel_booking or request_date_change, which is why it is not 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?

Usage is only implied: an agent can infer it should call this when a traveller needs to raise a complaint or issue. There is no explicit guidance on when to prefer this over self-service siblings like cancel_booking, request_date_change, or preview_cancellation, and no suggestion to check list_support_cases for an existing case first.

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