Skip to main content
Glama

aitrips.io

by io.aitrips
OverviewDiscussionsAdmin

trip_create

Create a new trip

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesTrip name (e.g., "London Christmas 2026")
endDateYesEnd date (YYYY-MM-DD)
currencyNoCurrency code (USD, GBP, EUR)USD
timezoneNoTimezone (e.g., "Europe/London")UTC
startDateYesStart date (YYYY-MM-DD)
budgetTotalNoTotal budget
destinationYesDestination city/country
destinationLatNoDestination latitude (-90 to 90). Provide with destinationLng to center map.
destinationLngNoDestination longitude (-180 to 180). Provide with destinationLat to center map.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / destinationLat
      Added value: +{
+  "description": "Destination latitude (-90 to 90). Provide with destinationLng to center map.",
+  "type": "number"
+}
    • addedInput schema / properties / destinationLng
      Added value: +{
+  "description": "Destination longitude (-180 to 180). Provide with destinationLat to center map.",
+  "type": "number"
+}
  2. First observed

TDQS

C2.9/5.0
Behavior2/5

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

The description repeats the create action without disclosing side effects, validation behavior, defaults, ID generation, or post-creation effects. Annotations declare readOnlyHint and destructiveHint as false but do not compensate for the missing behavioral context.

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?

The description is a single short sentence with no wasted words and the key verb is front-loaded. It is concise, though arguably too sparse for a tool with nine parameters and no output schema.

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

Completeness2/5

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

With nine parameters, four required fields, and no output schema, the description provides no information about what the tool returns, how success is reported, or when creating a new trip is preferable to cloning/updating. The schema is rich, but the tool-level context remains incomplete.

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%, and each parameter already has meaningful descriptions, including formats, defaults, and coordinate guidance. The description adds no parameter-level meaning, so the baseline of 3 is appropriate.

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 states a clear verb and resource ('Create a new trip') and the word 'new' hints at a distinction from sibling trip_clone. It is not a full tautology, but it adds no detail beyond what the tool name and title already imply.

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

Usage Guidelines2/5

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

There is no guidance about when to use this tool versus alternatives such as trip_clone, trip_update, or trip_delete. The only implied usage is 'create a new trip,' with no exclusions or decision criteria.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All aitrips.io toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources