Skip to main content
Glama

suggest_new_note

Generates recommended IDs, paths, related notes, cross-links, and frontmatter templates for a new wiki note to keep atomic notes consistent and correctly linked.

Instructions

새 노트 작성 시 도움 — 관련 기존 노트, 권장 cross-link, 권장 위치, 권장 ID.

Wiki 일관성 유지의 핵심 도구.

Args: topic: 새 노트 주제 (예: "GraphRAG", "Sparse attention", "Llama Guard 4") top_k: 관련 기존 노트 수 (기본 8)

Returns: 권장 ID, 권장 경로, 관련 노트, 추가할 cross-link, frontmatter 템플릿

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

Input Schema

NameRequiredDescriptionDefault
top_kNo
topicYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

A3.5/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It discloses the output contents (recommended ID, path, related notes, cross-links, frontmatter template) and the 'suggest' framing implies nothing is written, but it never explicitly states that the wiki is unmodified or whether it depends on a fresh index. Adequate but not thorough for a zero-annotation tool.

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 summary line is front-loaded and the Args/Returns blocks are compact. The Returns section partly duplicates the existing output schema, which is minor waste, but nothing is padded or redundant at length.

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?

An output schema exists, so return values need not be re-explained; the description still names them for orientation, and both parameters are addressed. For a simple two-parameter advisory tool this is close to complete, with only the side-effect/indexing question left open.

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 0%, so the description must compensate. It does partially: topic is illustrated with three concrete examples and top_k is explained as 'number of related existing notes' with default 8, which adds real meaning beyond bare 'integer'/'string' types. It still omits constraints such as whether topic should be a short label vs. a phrase and any bounds on top_k.

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+resource pair: it produces suggestions (related notes, cross-links, path, ID, frontmatter) for a note that is about to be written, and frames itself as a wiki-consistency helper. That clearly separates it from create_note, which actually writes. It never names find_related or list_templates, so the boundary with those is left implicit.

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?

"When writing a new note" is stated as the trigger condition and 'core tool for wiki consistency' signals importance, but there is no explicit when-not guidance and no named alternative. An agent must infer that this is a pre-creation advisory step rather than a search or creation step.

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