Skip to main content
Glama
Sign In
Voicenotes MCP

Voicenotes MCP

by mayankbohradev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

vn_delete_note

Destructive

Delete a note by providing its ID and setting confirm to true to prevent accidental removal.

Instructions

[Group C / unconfirmed endpoint] Delete a note. Requires confirm:true to attempt.

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": "vn_delete_note"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesNote id
confirmNoMust be true to actually delete

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already indicate destructive hint, but the description adds the crucial detail that a confirm parameter must be true to actually delete, which prevents accidental destruction. This goes beyond the annotations.

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 with two short sentences. Every word is necessary and there is no fluff.

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?

Given the simplicity of the tool (2 parameters, no output schema), the description covers the essential behavior. It could mention what happens on success/failure, but the core delete operation is well explained.

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?

The input schema already fully describes the parameters (id and confirm) with descriptions. The tool description adds no new meaning beyond the schema, so baseline score 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 clearly states it's for deleting a note, distinguishing it from other note operations like update or create. It's specific and unambiguous.

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

Usage Guidelines3/5

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

The description mentions the confirm:true requirement, providing a clear usage condition. However, it does not explicitly discuss when to use this tool versus alternatives (e.g., updating instead of deleting).

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

Deploy Server

Other Tools