Your Next Tours

Delete Trip Stop

delete_trip_item

DestructiveIdempotent

Delete a trip stop. Params: id (trip uuid), itemId (uuid). NO notification is sent.

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>",
      "itemId": "<itemId>"
    },
    "name": "delete_trip_item"
  }
}

Input Schema

Name	Required	Description	Default
`id`	Yes
`itemId`	Yes

Output Schema

Name	Required	Description	Default
`id`	No
`label`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 2, 2026

TDQS

B3/5.0

Behavior3/5

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

Annotations already declare destructiveHint=true, idempotentHint=true and readOnlyHint=false, so the safety profile is covered. The description adds one genuinely useful piece of behavioral context not in annotations: 'NO notification is sent.' It omits permission requirements, whether the delete is hard or soft, and behavior on a missing item.

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 fragments, action front-loaded, zero filler. Slightly terse rather than over-written, but nothing is wasted.

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?

An output schema exists so return values need not be explained, and annotations cover the destructive/idempotent profile. However, for a destructive mutation the description says nothing about permissions, side effects on ordering, or failure behavior with an invalid itemId.

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

Parameters2/5

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

Schema description coverage is 0% and both params are required, so the description must carry the meaning. It labels id as the 'trip uuid' (useful) but describes itemId only as '(uuid)', giving no indication that it identifies the specific trip stop to remove.

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: 'Delete a trip stop', which is unambiguous against add_trip_item/update_trip_item. It does not differentiate itself from the broader delete_trip or delete_template_schedule_stop siblings, but the action on a trip stop is clear.

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 on when to use this versus update_trip_item or set_trip_item_status, nor any prerequisite or exclusion. The agent is left to infer usage entirely from the name.

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?