Skip to main content
Glama

Prepare an inquiry

request_inquiry
Idempotent

Prepares an inquiry for one offer, for when the user has asked to inquire and given their email. voidjet emails the user a link; nothing is forwarded to the provider until the user opens it and sends the pre-filled form on voidjet.io within 48 hours. name, phone and message are optional, come from the user and only pre-fill the form. Prices are indicative.

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": {
      "ref": "<ref>",
      "email": "<email>",
      "passengers": "<passengers>"
    },
    "name": "request_inquiry"
  }
}

Input Schema

NameRequiredDescriptionDefault
refYesref exactly as returned by search_empty_legs.
nameNoThe user's name, only if the user gave it.
emailYesThe user's email address.
phoneNoThe user's phone number, only if the user gave it.
localeNoLanguage of texts and links in the result: en or de.en
messageNoMessage to the provider in the user's own words, optional.
flexibleNoTrue if the user is flexible on date and time.
passengersYesNumber of passengers travelling.

Output Schema

NameRequiredDescriptionDefault
statusYes
messageYes
expires_atYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changed
    • addedInput schema / properties / flexible / description
      Added value: +"True if the user is flexible on date and time."
    • addedInput schema / properties / locale / description
      Added value: +"Language of texts and links in the result: en or de."
    • addedInput schema / properties / message / description
      Added value: +"Message to the provider in the user's own words, optional."
    • addedInput schema / properties / name / description
      Added value: +"The user's name, only if the user gave it."
    • addedInput schema / properties / passengers / description
      Added value: +"Number of passengers travelling."
    • addedInput schema / properties / phone / description
      Added value: +"The user's phone number, only if the user gave it."
  2. Added

TDQS

A4.1/5.0
Behavior5/5

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

The annotations only declare the safety profile (readOnly=false, destructive=false, idempotent, open-world); the description adds genuinely new behavior: voidjet emails the user a link, nothing reaches the provider until the user submits the pre-filled form on voidjet.io within 48 hours, and prices are non-binding. This is exactly the side-effect and timing information an agent needs before invoking a tool that sends mail.

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?

Front-loads the purpose and precondition, then the side effect, then the field semantics in four tight sentences. The 48-hour clause is packed into a long sentence and the trailing 'Prices are indicative.' is somewhat abrupt, but virtually every sentence carries distinct information.

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

Completeness5/5

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

With 8 parameters, an output schema, full schema coverage and annotations in place, the description supplies the remaining pieces an agent needs: who receives what, when the provider is actually contacted, the 48-hour expiry of the link, and the non-binding nature of prices. Nothing essential for correct invocation is missing.

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 100%, so the schema already documents ref, locale, passengers, flexible and the optional fields in detail. The description reinforces that name/phone/message are optional, user-supplied, and only pre-fill the form, but adds nothing about ref format, passenger limits, or locale effects beyond what the schema says, so this is the baseline 3.

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?

States a specific verb and resource ('Prepares an inquiry for one offer'), which implicitly separates it from the sibling request_charter_quote (a quote request vs. an inquiry). No sibling is named explicitly, so the differentiation is inferred rather than stated, keeping it just below the top mark.

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?

Gives a clear triggering condition: only when 'the user has asked to inquire and given their email,' which also functions as a precondition on the required email/ref. It does not name when NOT to use it (e.g., when the user wants a firm price or a charter quote instead), so it falls short of a 5.

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