Your Next Tours

Delete Trip

delete_trip

Destructive

Permanently DELETE a trip (a wrong or duplicate departure, or one whose program was deleted). Works only on a trip that has no (joined) participants and is not completed; for a trip with participants use announce_trip_cancellation. NO notification is sent. Params: id (trip uuid).

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": {
      "id": "<id>"
    },
    "name": "delete_trip"
  }
}

Input Schema

Name	Required	Description	Default
`id`	Yes

Output Schema

Name	Required	Description	Default
`id`	No
`deleted`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 2, 2026

TDQS

A4.6/5.0

Behavior4/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, but the description adds non-derivable traits: the deletion is permanent, no notification is sent to anyone, and it will only succeed on participant-free, non-completed trips. It stops short of covering auth/permission requirements or the failure response, which keeps it just below a 5.

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 critical constraint (permanent deletion) and the routing alternative are front-loaded, and the parenthetical examples add genuine disambiguation rather than filler. It is dense, packing preconditions, alternatives, and the param note into three compact sentences, though slightly cramped.

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?

For a destructive single-param tool with an output schema available, everything an agent needs is present: what is destroyed, permanence, notification behavior, preconditions, and the sibling to use instead. Return values need not be described since an output schema exists.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must carry the parameter burden; it does by naming 'id (trip uuid)', which resolves which identifier the required field expects. The schema already supplies the uuid format and pattern, so no further syntax detail is needed for a single required param.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Permanently DELETE a trip') and immediately narrows applicability to wrong/duplicate departures or trips whose program was deleted. It distinguishes itself from the sibling delete_trip_item and from announce_trip_cancellation, so an agent can select it without opening a schema.

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

Usage Guidelines5/5

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

Gives explicit preconditions ('only on a trip that has no (joined) participants and is not completed') and an explicit alternative plus the condition that selects it ('for a trip with participants use announce_trip_cancellation'). This is exactly the when-to-use / when-not-to-use routing an agent needs.

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

All Your Next Tours tools Inspect

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

Need Help?