Skip to main content
Glama
istefox

istefox-dt-mcp

Official
by istefox

bulk_apply

Apply up to 500 add-tag, remove-tag, or move operations on DEVONthink records in a single batch call. Preview with dry-run, then confirm to commit; halts on first error for partial undo.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
inputYesApply many small ops in one call. Dry-run by default. Same preview-then-apply contract as `file_document`: call once with `dry_run=true` to inspect the planned operations and receive a `preview_token` (audit_id), then call again with `dry_run=false` + `confirm_token=<previous preview_token>` to commit. Failure semantics: DEVONthink has no transactions, so we cannot automatically roll back already-applied ops. Default is `stop_on_first_error=true` — the batch halts at the first failure and `failed_index` reports the offending op. The audit log records the partial state; the user can selectively undo applied ops by audit_id. Limits: max 500 ops per call. When to use: - Tag many records with the same tag. - Move a curated set of records to a single destination group. - Combine a few tag/move ops on the same set of records. Don't use for: - Single-record tagging/move — use `apply_tag`/`move_record` flows via `file_document` for richer audit (before_state). - Auto-classification — use `file_document` (calls DT classifier).

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
dataNo
successYes
audit_idNo
warningsNo
error_codeNo
error_messageNo
recovery_hintNo
Behavior1/5

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

Tool has no description.

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

Conciseness1/5

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

Tool has no description.

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

Completeness1/5

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

Tool has no description.

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

Parameters1/5

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

Tool has no description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

Tool has no description.

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

Usage Guidelines1/5

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

Tool has no description.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/istefox/istefox-dt-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server