Skip to main content
Glama

Bring a markdown file on this machine in as a document

import_doc

Imports a Markdown file from disk into Tisty as a document, copies its linked images, video, and PDFs into Tisty, and rewrites links to local copies while leaving the original file untouched.

Instructions

Read one markdown file from disk and keep it here as a document, turning on the way in what the Tisty language has no word for into what it can say, and saying what it changed. Every file the text points at beside it — pictures, video, PDFs — is copied in too, and the text is pointed at Tisty's own copies: nothing is left pointing outside. What cannot come in has its link taken out rather than left dangling. The files on disk are left untouched. Nothing is turned away for what it holds: a document carrying what looks like a live credential comes in as written, with a warning at the top for the person to decide about. A task's page brought back hands the task its properties and its words, and makes no document. Takes folder and page_of like write_doc. One file per call — walk an export folder yourself and call it for each, so the person sees what happened to each one.

Input Schema

NameRequiredDescriptionDefault
pathYesA markdown file under Downloads, Documents, Pictures, Desktop or the temporary folder
titleNoA title to put at the top, for a file whose first line is not one. Left out, the file name is used
anywayNoBring it in although a document on the same subject is here already — only when this really is another subject; otherwise update that one
folderNoThe 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
page_ofNoThe id of the document this becomes a page of

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior5/5

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

With no annotations provided, the description carries the full behavioral burden and does so thoroughly: source files remain untouched, linked assets are copied and repointed, dangling links are removed, secrets are imported with a warning rather than rejected, and task-page imports have a distinct outcome. These are important behaviors beyond what the schema declares.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The first sentence establishes the core action, but the description is a dense run-on paragraph with indirect phrasing such as 'turning on the way in what the Tisty language has no word for into what it can say.' Most sentences contain useful information, but the structure makes it harder to scan than necessary.

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

Completeness5/5

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

For a complex import tool with no annotations and no output schema, the description covers the key operational details: conversion, asset handling, link rewriting, source-file safety, secret handling, special task-page behavior, and iteration expectations. It is complete enough for an agent to understand what will happen on import.

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 the schema already explains all five parameters in detail. The description adds only that folder and page_of behave like write_doc, which is a small extra signal but does not otherwise deepen parameter semantics.

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 states a specific verb and resource: read one markdown file from disk and keep it as a document. It also describes the conversion, asset copying, and link rewriting that distinguish import_doc from siblings like write_doc or read_doc.

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 gives clear operational guidance: one file per call, walk export folders yourself, and a special rule that a task's page import hands properties to the task rather than creating a document. It does not explicitly compare against write_doc or clearly state when not to use import_doc, but the context is otherwise clear.

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