Skip to main content
Glama
Sign In
devonthink3-mcp

devonthink3-mcp

by waylake
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

dt3_list_group

Read-onlyIdempotent

List direct children of a DEVONthink group, including empty groups and records without indexed text. Use offset and limit to page results and continue via next_offset.

Instructions

Browse direct children, including empty groups and records without indexed text. Follow next_offset to continue.

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": {
      "uuid": "<uuid>"
    },
    "name": "dt3_list_group"
  }
}

Input Schema

NameRequiredDescriptionDefault
uuidYesRecord UUID or x-devonthink-item:// link. Link page/search parameters are ignored.
limitNo
offsetNo

Output Schema

NameRequiredDescriptionDefault
kindNo
recordsYes
advisoryNo
snapshotYes
next_offsetYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.3.0
    • changedInput schema / properties / limit / maximum
      Previous value: -100New value: +200
  2. First observedv0.2.0

TDQS

B3.1/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, non-destructive, closed-world behavior, so the bar is lower. The description still adds useful behavioral context beyond annotations: empty groups and records without indexed text are returned, and pagination continues via next_offset. It omits permission needs and rate limits, but for a read-only listing that is minor.

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?

Two short sentences, front-loaded with the inclusion guarantee and ending with the pagination instruction. Slightly terse since it never defines what a 'child' is or that uuid must identify a group, but there is no wasted wording.

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?

An output schema exists, so return-value detail needn't be explained, and the description usefully notes inclusion of empty groups and unindexed records. Still, with the subject unstated ('children of what?') and limit semantics undocumented, it is only minimally complete for a paginated listing tool with a partially documented schema.

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 33%, so uuid (with link handling) is documented but limit and offset are not. The description partly compensates by naming next_offset, implying offset is a continuation cursor, but it says nothing about limit or default/maximum page size.

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

Purpose3/5

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

The description says 'Browse direct children' — a verb-ish action plus the resource (children of a group) — and adds that empty groups and unindexed records are included. However, it never explicitly says it lists the children of a specific group identified by uuid, leaving the agent to infer the target from the required 'uuid' parameter.

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

Usage Guidelines2/5

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

No when-to-use or when-not-to-use guidance is given. It does not point to dt3_get_record or dt3_search as alternatives for fetching a single record or searching text, and gives no prerequisites (for example, that uuid should identify a group for meaningful results).

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

Deploy Server

Other Tools