Skip to main content
Glama
Sign In
wiznote-mcp

wiznote-mcp

by 735140144
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

wiz_create_note

Create a note with HTML or Markdown content, requiring title and category, for document management in your WizNote server.

Instructions

Create a note from HTML or Markdown.

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": {
      "title": "<title>",
      "category": "<category>"
    },
    "name": "wiz_create_note"
  }
}

Input Schema

NameRequiredDescriptionDefault
htmlNo
titleYes
kbGuidNo
categoryYes
markdownNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are provided, and the description lacks information on behavioral traits such as whether the tool overwrites existing notes, authorization requirements, or rate limits. It only states the basic action.

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?

The description is a single sentence, concise and front-loaded. However, it may be too brief, sacrificing essential detail for brevity.

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?

Given the tool has 5 parameters and no output schema or annotations, the description is incomplete. It fails to explain key aspects like parameter usage, return values, or constraints (e.g., mutual exclusivity of html and markdown).

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 the description adds minimal parameter information. It mentions HTML and Markdown but does not explain the purpose of parameters like kbGuid, category, or the relationship between html and markdown.

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 (create) and resource (note) and specifies input formats (HTML or Markdown). It distinguishes the tool from siblings like wiz_create_folder and wiz_get_note by the action and resource.

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 alternatives (e.g., wiz_update_note, wiz_search_notes). It does not mention context or prerequisites.

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