trip_note_delete
Destructive
Delete a note
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| noteId | Yes | Note ID |
aitrips.io
by io.aitrips
TDQS
B3.2/5.0
Behavior2/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The annotations already declare destructiveHint=true and readOnlyHint=false, so the destructive nature is externally covered. The description adds no behavioral context beyond what annotations provide, such as permanence, cascading effects, or whether confirmation is needed.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness5/5
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is extremely concise, containing only the essential verb and object with no filler. All information is front-loaded, and nothing is wasted.
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?
For a simple one-parameter destructive tool, the description plus the annotation and schema provide enough information for an agent to invoke it correctly. It is slightly incomplete in that it does not clarify the 'trip note' scope, but the tool name and sibling context fill that gap.
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%: the 'noteId' parameter is already documented as 'Note ID'. The description adds no additional semantic meaning, so the baseline score 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 states a specific verb ('Delete') and a resource ('a note'), which is clear and not a tautology. However, it does not explicitly distinguish trip notes from other delete-capable resources, though the tool name and title help disambiguate.
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?
The description provides no guidance on when to use this tool versus siblings like trip_note_update, trip_note_list, or trip_delete. There are no conditions, exclusions, or alternative recommendations, leaving the agent to infer usage solely from the name and schema.
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.
TDQS
B3.1/5.0
Disambiguation4/5
Most tools are clearly separated by resource type and action, making selection. The main ambiguity is between trip_item_add and trip_transport_add, since trip_item_add lists transport as a category but trip_transport_add explicitly says to always use it instead for transport.
Naming Consistency4/5
The naming pattern is highly consistent: trip_<resource>_<action>. Minor deviations exist with bare verbs like search and fetch, and trip_review uses a verb-only style, but these are easy to understand within the larger pattern.
Tool Count2/5
37 tools is a large surface that exceeds the typical coherence threshold. While the domain is broad, the count makes the server feel heavy and harder for an agent to navigate compared to a more focused toolset.
Completeness4/5
The toolset provides strong CRUD/lifecycle coverage across trips, items, notes, tasks, locations, collaborators, shares, and transport, plus review and search capabilities. Minor gaps exist, such as no direct collaborator add, no location update, and no item-level comment delete, but these are workable.