Skip to main content
Glama

Report an unmet need

report_unmet_need

Records a need voidjet cannot serve, for when the user wants voidjet to know about it: e.g. no offer on the route, a return flight, pets, instant booking. Takes 1-5 categories and optional route, dates, passengers and budget; no personal data. Helps voidjet decide what to add.

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": {
      "categories": "<categories>"
    },
    "name": "report_unmet_need"
  }
}

Input Schema

NameRequiredDescriptionDefault
originNoWanted departure city, airport code or region.
date_toNoLatest wanted travel date (YYYY-MM-DD).
date_fromNoEarliest wanted travel date (YYYY-MM-DD).
categoriesYesWhat the user needed that voidjet could not offer (1-5 categories).
passengersNoNumber of passengers.
destinationNoWanted arrival city, airport code or region.
aircraft_classNoWanted aircraft class, if the user named one.
max_budget_eurNoBudget in EUR for the whole aircraft.

Output Schema

NameRequiredDescriptionDefault
messageYes
recordedYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed8 schema fields changed
    • addedInput schema / properties / aircraft_class / description
      Added value: +"Wanted aircraft class, if the user named one."
    • addedInput schema / properties / categories / description
      Added value: +"What the user needed that voidjet could not offer (1-5 categories)."
    • addedInput schema / properties / date_from / description
      Added value: +"Earliest wanted travel date (YYYY-MM-DD)."
    • addedInput schema / properties / date_to / description
      Added value: +"Latest wanted travel date (YYYY-MM-DD)."
    • addedInput schema / properties / destination / description
      Added value: +"Wanted arrival city, airport code or region."
    • addedInput schema / properties / max_budget_eur / description
      Added value: +"Budget in EUR for the whole aircraft."
    • addedInput schema / properties / origin / description
      Added value: +"Wanted departure city, airport code or region."
    • addedInput schema / properties / passengers / description
      Added value: +"Number of passengers."
  2. 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 this is a non-read-only, non-destructive, non-idempotent write with no open-world effects, so the agent knows it persists data. The description adds useful constraints beyond that: 'no personal data', a 1-5 category cap, and the stated downstream purpose ('Helps voidjet decide what to add'). It does not say whether submissions are deduplicated, acknowledged, or what happens on repeat calls, which matters for a non-idempotent write.

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?

Three short sentences, front-loaded with the core action before examples and payload summary. The clause 'for when the user wants voidjet to know about it' is slightly redundant with 'Records a need', but the text is otherwise efficient.

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?

With 8 parameters, a rich enum of 23 categories, full schema coverage, annotations, and an output schema, the description supplies the intent, trigger conditions, and a privacy note. An agent can decide to call it and populate required fields confidently. The only missing piece is disambiguation from adjacent request/alert tools.

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 is already documented field-by-field. The description only restates the parameter groups (route, dates, passengers, budget) and gives loose examples of categories. That is a mild reinforcement of intent rather than new semantic meaning, so the baseline of 3 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 gives a concrete verb and resource: 'Records a need voidjet cannot serve', followed by example triggers (no offer on the route, pets, instant booking). The action and payload shape are immediately clear. It stops short of naming the sibling tool an agent should prefer when the user actually wants a notification or quote, so it is clear but not differentiated.

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 states the condition for use: 'when the user wants voidjet to know about it', and lists the situations that qualify (no offer on route, return flight, pets, instant booking). No explicit when-not or alternative is given — notably the 'notification_on_new_offers' category overlaps conceptually with alert-style siblings — but the usage context is clear enough to act on.

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