Skip to main content
Glama
Sign In
Voicenotes MCP

Voicenotes MCP

by mayankbohradev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

vn_get_note

Read-only

Retrieve a note by its ID to access the full transcript and associated tags.

Instructions

Get one note by id, including its full transcript and tags.

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_get_note"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesNote id / UUID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the tool is known to be safe and non-destructive. The description adds value by specifying the return content (full transcript and tags), which 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 a single, well-crafted sentence that contains no unnecessary words. It efficiently communicates the tool's core functionality.

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 simple input (one required parameter) and no output schema, the description adequately covers what the tool returns. It could mention handling of non-existent IDs, but that is not essential for a read operation.

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 coverage is 100% for the single parameter 'id', which is described as 'Note id / UUID'. The description does not add any additional parameter information beyond what the schema already provides.

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?

The description clearly states the action ('Get one note by id') and explicitly mentions what is included ('full transcript and tags'). It distinguishes this from sibling tools like vn_list_notes and vn_search_notes, which handle multiple notes or search results.

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 implicitly indicates that the tool is for fetching a single note by ID, but it does not provide explicit when-to-use guidance or contrast with alternatives such as using list_notes for multiple notes or search_notes for filtering.

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