Skip to main content
Glama
Sign In
Voicenotes MCP

Voicenotes MCP

by mayankbohradev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

vn_create_tag

Create a new tag with optional auto-tagging keywords, pin to top, and emoji. Organize your notes efficiently by setting up tags with automatic keyword matching.

Instructions

Create a tag with optional auto-tagging keywords, pin state, emoji.

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

Input Schema

NameRequiredDescriptionDefault
nameYesTag name
keywordsNoAuto-tag keywords
is_pinnedNoPin to top
emojiNoOptional emoji

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.4/5.0
Behavior3/5

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

Annotations indicate readOnlyHint=false and destructiveHint=false, which aligns with the create action. The description mentions optional features but omits behavioral details like duplicate handling, return value, or side effects. Adequate but not rich.

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?

Single sentence that is front-loaded with the core action. No unnecessary words; every part adds value.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

No output schema, so description should explain return value (e.g., created tag ID). Tool has 4 parameters and siblings, but description is too brief to cover all aspects needed for correct invocation.

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%, and description mentions the same parameters as schema descriptions. No additional meaning or constraints beyond what schema provides. Baseline of 3 is appropriate.

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?

Description clearly states the action ('Create') and resource ('tag'), and lists optional attributes (auto-tagging keywords, pin state, emoji). It distinguishes from siblings like vn_update_tag or vn_delete_tag.

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?

No guidance on when to use this tool versus alternatives like vn_bulk_tag_notes or vn_setup_tags. The description doesn't include when-not-to-use or prerequisite conditions.

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