Skip to main content
Glama

import_markdown_context

Imports hierarchical Markdown into an existing mind map, converting headings and nested lists into elements and optionally nesting them under a parent.

Instructions

任意の深さのMarkdown(インデントで階層を表現したリスト、見出しは#)を組み立てて、既存のマップに流し込む。見出しも1つの要素として取り込む。取り込み先がTODOマップでない場合、- [ ]/- [x]のチェックボックス記法は取り除かれチェック状態も反映されない(アプリ本体の挙動と同じ)。対象は既存マップのみ(新規作成が必要ならcreate_mapを先に呼ぶ)。

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": {
      "mapId": "<mapId>",
      "markdown": "<markdown>"
    },
    "name": "import_markdown_context"
  }
}

Input Schema

NameRequiredDescriptionDefault
mapIdYeslist_mapsで得たマップのID
markdownYes取り込むMarkdownテキスト(1要素5000文字まで。超える要素があれば何も書かない)。要素の1行目に「📅 2026-10-15」(期日)・「🛫 2026-10-12」(着手日)と書くと日付として取り込む。時刻付きは「📅 2026-10-15 09:00」(アプリで設定しているタイムゾーンの時刻)
parentElementIdNoこの要素の内側(子)として取り込む。マップの最上位に取り込む場合はnullまたは省略

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.5.0
    • changedInput schema / properties / markdown / description
      Previous value: -"取り込むMarkdownテキスト(1要素5000文字まで。超える要素があれば何も書かない)。要素の1行目に「📅 2026-10-15」(期日)・「🛫 2026-10-12」(着手日)と書くと日付として取り込む。時刻付きは「📅 2026-10-15 09:00」(このPCの現地時刻)"New value: +"取り込むMarkdownテキスト(1要素5000文字まで。超える要素があれば何も書かない)。要素の1行目に「📅 2026-10-15」(期日)・「🛫 2026-10-12」(着手日)と書くと日付として取り込む。時刻付きは「📅 2026-10-15 09:00」(アプリで設定しているタイムゾーンの時刻)"
  2. Changed1 schema field changedv0.3.0
    • changedInput schema / properties / markdown / description
      Previous value: -"取り込むMarkdownテキスト"New value: +"取り込むMarkdownテキスト(1要素5000文字まで。超える要素があれば何も書かない)。要素の1行目に「📅 2026-10-15」(期日)・「🛫 2026-10-12」(着手日)と書くと日付として取り込む。時刻付きは「📅 2026-10-15 09:00」(このPCの現地時刻)"
  3. First observedv0.1.2

TDQS

A4/5.0
Behavior3/5

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

With no annotations, the description bears full burden. It discloses useful behavior — headings count as elements, checkbox markers are stripped on non-TODO maps, existing maps only — which is real value beyond structured fields. However, it never says whether the import appends to or replaces existing map contents, what is returned (no output schema), or how failures are surfaced; the all-or-nothing 5000-char rule lives only in the schema, and permission requirements are unstated.

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?

Three dense sentences, front-loaded with the core action, then behavior caveats, then the prerequisite. No filler. It is slightly run-on, packing three clauses into the first parenthetical, but every sentence carries information.

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

Completeness3/5

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

For a 3-parameter mutation tool with no annotations and no output schema, the definition covers input format and prerequisites well. It is still incomplete on outcome semantics: whether existing map content is preserved or overwritten, what the response contains, and what happens when only some elements exceed limits. Those gaps matter for an agent deciding whether to call it destructively.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so a baseline of 3 applies, but the description adds meaning the schema does not: indentation expresses list hierarchy and `#` marks headings, both of which are also imported as elements. That is genuine format semantics for the `markdown` parameter beyond its schema text. It adds nothing new for parentElementId, which the schema already explains.

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 names a specific action (building Markdown of arbitrary depth and importing it into an existing map) and a specific resource (mapId). It further clarifies that headings become elements and how checkbox syntax is handled, so an agent knows exactly what gets written, not just that something is 'imported'.

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

Usage Guidelines4/5

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

It states an explicit precondition (target must be an existing map) and routes to the alternative (call create_map first if a new map is needed). It also flags the non-TODO-map caveat where checkbox state is lost. It stops short of contrasting with per-element tools like edit_element or move_element, but the core when-to-use guidance is present.

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