Skip to main content
Glama
Sign In
Devon

Devon

by mnott
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

create_summary_document

Generate AI-powered summary documents by consolidating multiple DEVONthink records into concise formats like markdown, key points, or tables for efficient information synthesis.

Instructions

Create an AI-generated summary document from multiple DEVONthink documents.

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": {
      "documentUuids": "<documentUuids>"
    },
    "name": "create_summary_document"
  }
}

Input Schema

NameRequiredDescriptionDefault
customTitleNoTitle for the new summary record. Defaults to 'Summary - <ISO date>' if omitted
summaryTypeNoOutput format for the summary document. One of: markdown, rich, sheet, simple. Defaults to markdown
summaryStyleNoStyle of summary to generate. One of: text summary, key points summary, list summary, table summary, custom summary
documentUuidsYesUUIDs of the source DEVONthink records to summarize
parentGroupUuidNoUUID of the group where the summary document should be created. If omitted, the summary is placed in the same group as the first source record

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv3.0.1

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations provided, the description carries the full burden. It appropriately flags the 'AI-generated' nature (indicating non-deterministic output), but omits critical behavioral details: whether the operation is idempotent, what happens if source documents are missing, storage implications, or whether the created document maintains links to sources.

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?

The description is a single, efficient sentence with no redundancy. However, it may be overly terse given the tool's complexity (AI generation with 5 parameters) and the absence of annotations or output schema, leaving room for additional context without sacrificing clarity.

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?

The description covers the core function adequately for a simple tool, but given the AI complexity and lack of annotations/output schema, it omits important context: default behaviors (implied by schema but not described), error handling for invalid UUIDs, and whether the summary updates automatically when sources change.

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?

The schema has 100% description coverage, establishing a baseline of 3. The description mentions 'multiple DEVONthink documents' which aligns with 'documentUuids', but adds no additional context about parameter interactions (e.g., how 'summaryStyle' affects output when combined with 'summaryType') or validation constraints beyond the schema.

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?

The description clearly states the specific action ('Create'), the nature of the output ('AI-generated summary document'), and the input source ('multiple DEVONthink documents'). It implicitly distinguishes from sibling 'create_record' by specifying AI-generated content, and from 'ask_ai_about_documents' by focusing on document creation rather than Q&A, though explicit differentiation is absent.

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?

The description provides no guidance on when to use this tool versus alternatives like 'ask_ai_about_documents' (for interactive Q&A) or 'create_record' (for manual content). It lacks prerequisites (e.g., requiring valid DEVONthink document UUIDs) and exclusion criteria.

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