Skip to main content
Glama
mnott

Devon

by mnott
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Local

get_record_properties

Retrieve comprehensive metadata and properties for DEVONthink records, including type, size, dates, tags, and location details using UUID, record ID, or path identifiers.

Instructions

Get detailed properties and metadata for a DEVONthink record. Returns uuid, name, type, path, location, database, size, dates, tags, comment, url, kind, mimeType, flagged, locking, wordCount, and more. Provide uuid (preferred), recordId + databaseName, or recordPath + databaseName.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
uuidNoUUID of the record
recordIdNoNumeric record ID (requires databaseName)
recordPathNoRecord path within the database (requires databaseName)
databaseNameNoDatabase name (required for recordId or recordPath lookups)

Implementation Reference

  • src/tools/records/get-record-properties.ts:13-46 (handler)
    The definition and handler implementation for the `get_record_properties` tool. It uses JXA to interact with DEVONthink to fetch record metadata.
    export const getRecordPropertiesTool = defineTool({
  name: "get_record_properties",
  description:
    "Get detailed properties and metadata for a DEVONthink record. " +
    "Returns uuid, name, type, path, location, database, size, dates, tags, " +
    "comment, url, kind, mimeType, flagged, locking, wordCount, and more. " +
    "Provide uuid (preferred), recordId + databaseName, or recordPath + databaseName.",
  schema: z.object({
    uuid: z.string().optional().describe("UUID of the record"),
    recordId: z.number().int().nonnegative().optional().describe("Numeric record ID (requires databaseName)"),
    recordPath: z.string().optional().describe("Record path within the database (requires databaseName)"),
    databaseName: z.string().optional().describe("Database name (required for recordId or recordPath lookups)"),
  }),
  run: async (args, executor) => {
    const { uuid, recordId, recordPath, databaseName } = args;

    const script = `
      ${JXA_APP}
      var uuid = ${jxaLiteral(uuid ?? null)};
      var recordId = ${jxaLiteral(recordId ?? null)};
      var recordPath = ${jxaLiteral(recordPath ?? null)};
      var recordName = null;
      var dbName = ${jxaLiteral(databaseName ?? null)};

      ${JXA_RESOLVE_DB}
      ${JXA_RESOLVE_RECORD}

      JSON.stringify(${JXA_RECORD_PROPS});
    `;

    const result = executor.run(script);
    return JSON.parse(result.stdout);
  },
});

Tool Definition Quality

A4/5.0
Behavior3/5

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

No annotations provided, so description carries full burden. The verb 'Get' implies read-only behavior, but lacks explicit safety declaration (readOnlyHint). Compensates by extensively listing return fields (uuid, name, type, etc.) since no output schema exists, though this describes output format rather than behavioral traits like side effects or rate limits.

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

Conciseness5/5

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

Three sentences with zero waste: purpose declaration, return value enumeration, and parameter usage pattern. Front-loaded with the core action, followed by specific details. No redundant or filler text.

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?

Well-compensated for missing output schema by listing extensive return fields. Parameter lookup patterns are clear. Only gap is lack of explicit read-only/safety declaration given zero annotations, though 'Get' strongly implies this.

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

Parameters4/5

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

Despite 100% schema coverage, the description adds significant value by explaining parameter relationships and constraints: that uuid can be used alone while recordId/recordPath require databaseName, and that uuid is 'preferred'. This relational context is absent from the individual schema field descriptions.

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?

Clear verb ('Get') + specific resource ('detailed properties and metadata') + scope ('DEVONthink record'). Explicitly targets properties/metadata, distinguishing from siblings like get_record_content (likely returns file content) and lookup_record (likely returns basic identifiers).

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?

Provides implicit guidance by specifying three valid lookup patterns ('uuid preferred', 'recordId + databaseName', 'recordPath + databaseName'). However, lacks explicit when-to-use guidance versus similar lookup siblings like get_record_by_identifier or lookup_record.

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/mnott/Devon'

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