Skip to main content
Glama

Bring a Markdown file in as a document

import_doc
Destructive

Imports a Markdown file from disk into Tisty as a document, converts it to Tisty language, reports changes, pulls in linked files, and leaves the original untouched.

Instructions

Bring one Markdown file from disk in as a document, turned into the Tisty language, saying what changed. Files it points at come in too; links to what cannot are taken out. The file on disk is untouched; a seeming live credential comes in under a warning. A task's exported page goes back to its task. One file per call.

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

Input Schema

NameRequiredDescriptionDefault
pathYesA Markdown file under Downloads, Documents, Pictures, Desktop or the temporary folder
titleNoA title for a file whose first line is not one; defaults to the file name
anywayNoBring it in although a document has the same subject; only when it truly is another
folderNoThe existing folder its subject belongs in, by name, path or id. Left out needs a reason
page_ofNoId of the document it becomes a page of

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv1.43.2
    • changedInput schema / properties / anyway / description
      Previous value: -"Bring it in although a document on the same subject is here already — only when this really is another subject; otherwise update that one"New value: +"Bring it in although a document has the same subject; only when it truly is another"
    • changedInput schema / properties / folder / description
      Previous value: -"The existing folder its subject belongs in, by its name, its whole path or its id. Expected: left out, it sits outside them all, and that needs a reason"New value: +"The existing folder its subject belongs in, by name, path or id. Left out needs a reason"
    • changedInput schema / properties / page_of / description
      Previous value: -"The id of the document this becomes a page of"New value: +"Id of the document it becomes a page of"
    • changedInput schema / properties / path / description
      Previous value: -"A markdown file under Downloads, Documents, Pictures, Desktop or the temporary folder"New value: +"A Markdown file under Downloads, Documents, Pictures, Desktop or the temporary folder"
    • changedInput schema / properties / title / description
      Previous value: -"A title to put at the top, for a file whose first line is not one. Left out, the file name is used"New value: +"A title for a file whose first line is not one; defaults to the file name"
  2. First observed

TDQS

A3.9/5.0
Behavior5/5

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

Goes well past the annotations by disclosing recursive import of referenced files, stripping of unresolvable links, a warning path for credential-like content, round-tripping of a task's exported page, and that the source file on disk is left untouched. The last point usefully scopes the destructiveHint=true to the destination workspace rather than the source, which prevents a costly misread.

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?

Front-loads the core action and packs distinct facts into short clauses; nothing is redundant. Some sentences are terse to the point of opacity ('A task's exported page goes back to its task'), which costs a little clarity but not 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?

Covers the return value ('saying what changed') in lieu of an output schema, and the recursive/credential/round-trip behaviors are the ones an agent most needs before a destructive import. It stops short of explaining what happens when a matching subject already exists — the very scenario the 'anyway' and 'folder' parameters exist for.

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 description coverage is 100%, so baseline applies. The description does not explain title, anyway, folder, or page_of at all — notably it never explains the collision behavior that 'anyway' and 'folder' imply, so it adds no meaning beyond the schema here.

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?

States a concrete verb and resource ('Bring one Markdown file from disk in as a document') and adds the transformation ('turned into the Tisty language') plus a scope limit ('One file per call'). It doesn't name any sibling such as write_doc or file_doc, so an agent must infer that this is the from-disk path, but the purpose itself is unambiguous.

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?

Usage is only implied: the mention of a file 'from disk' and 'One file per call' hints at when this beats authoring tools, but there is no explicit when-to-use, when-not, or named alternative. Nothing tells the agent whether to prefer write_doc for net-new content or attach for non-Markdown material.

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