Skip to main content
Glama
its-dart

Dart MCP Server

by its-dart

list_docs

Retrieve and filter documents in Dart with parameters like folder, title, content, or trash status. Supports pagination and ordering for efficient document management.

Instructions

List docs from Dart with optional filtering parameters. You can filter by folder, title, text content, and more.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
folderNoFilter by folder title
folderIdNoFilter by folder ID
idsNoFilter by IDs
inTrashNoFilter by trash status
limitNoNumber of results per page
oNoOrdering options (use - prefix for descending)
offsetNoInitial index for pagination
sNoSearch by title, text, or folder title
textNoFilter by text content
titleNoFilter by title

Implementation Reference

  • Handler for the 'list_docs' tool in the MCP CallToolRequestSchema switch statement. It calls DocService.listDocs(args) and returns the JSON stringified result.
    case LIST_DOCS_TOOL.name: {
      const docs = await DocService.listDocs(args);
      return {
        content: [{ type: "text", text: JSON.stringify(docs, null, 2) }],
      };
  • Schema definition for the 'list_docs' tool, including name, description, and detailed inputSchema for filtering docs.
    export const LIST_DOCS_TOOL: Tool = {
      name: "list_docs",
      description:
        "List docs from Dart with optional filtering parameters. You can filter by folder, title, text content, and more.",
      inputSchema: {
        type: "object",
        properties: {
          folder: { type: "string", description: "Filter by folder title" },
          folderId: {
            type: "string",
            description: "Filter by folder ID",
            pattern: "^[a-zA-Z0-9]{12}$",
          },
          ids: { type: "string", description: "Filter by IDs" },
          inTrash: { type: "boolean", description: "Filter by trash status" },
          limit: { type: "number", description: "Number of results per page" },
          offset: { type: "number", description: "Initial index for pagination" },
          text: { type: "string", description: "Filter by text content" },
          title: { type: "string", description: "Filter by title" },
          o: {
            type: "array",
            items: {
              type: "string",
              enum: [
                "-created_at",
                "-order",
                "-title",
                "-updated_at",
                "created_at",
                "order",
                "title",
                "updated_at",
              ],
            },
            description: "Ordering options (use - prefix for descending)",
          },
          s: {
            type: "string",
            description: "Search by title, text, or folder title",
          },
        },
        required: [],
      },
    };
  • index.ts:192-214 (registration)
    Registration of 'list_docs' tool (as LIST_DOCS_TOOL) in the TOOLS array, used by ListToolsRequestSchema handler.
    const TOOLS = [
      // Config
      GET_CONFIG_TOOL,
      // Tasks
      CREATE_TASK_TOOL,
      LIST_TASKS_TOOL,
      GET_TASK_TOOL,
      UPDATE_TASK_TOOL,
      DELETE_TASK_TOOL,
      // Docs
      CREATE_DOC_TOOL,
      LIST_DOCS_TOOL,
      GET_DOC_TOOL,
      UPDATE_DOC_TOOL,
      DELETE_DOC_TOOL,
      // Comments
      ADD_TASK_COMMENT_TOOL,
      LIST_TASK_COMMENTS_TOOL,
      // Other
      GET_DARTBOARD_TOOL,
      GET_FOLDER_TOOL,
      GET_VIEW_TOOL,
    ];
  • index.ts:371-373 (registration)
    MCP server request handler for ListToolsRequestSchema that returns the TOOLS array including 'list_docs'.
    server.setRequestHandler(ListToolsRequestSchema, async () => ({
      tools: TOOLS,
    }));
  • index.ts:36-52 (registration)
    Import of LIST_DOCS_TOOL from tools.js for use in index.ts.
      ADD_TASK_COMMENT_TOOL,
      CREATE_DOC_TOOL,
      CREATE_TASK_TOOL,
      DELETE_DOC_TOOL,
      DELETE_TASK_TOOL,
      GET_CONFIG_TOOL,
      GET_DARTBOARD_TOOL,
      GET_DOC_TOOL,
      GET_FOLDER_TOOL,
      GET_TASK_TOOL,
      GET_VIEW_TOOL,
      LIST_DOCS_TOOL,
      LIST_TASK_COMMENTS_TOOL,
      LIST_TASKS_TOOL,
      UPDATE_DOC_TOOL,
      UPDATE_TASK_TOOL,
    } from "./tools.js";
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. While it mentions filtering capabilities, it doesn't describe important behavioral aspects like whether this is a read-only operation, pagination behavior (implied by limit/offset but not explained), rate limits, authentication requirements, or what happens when no filters are applied. The description is insufficient for a tool with 10 parameters and no annotation coverage.

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 appropriately concise with two sentences that efficiently convey the core functionality. It's front-loaded with the main purpose and follows with filtering capabilities. No wasted words, though it could be slightly more structured.

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

Completeness2/5

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

For a tool with 10 parameters, no annotations, and no output schema, the description is inadequate. It doesn't explain what the tool returns (document list format), doesn't mention pagination behavior despite having limit/offset parameters, and provides minimal behavioral context. The description should do more to compensate for the lack of structured metadata.

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 documents all parameters thoroughly. The description adds minimal value by mentioning 'filter by folder, title, text content, and more' but doesn't provide additional context beyond what's in the schema. This meets the baseline for high schema coverage.

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 tool's purpose as 'List docs from Dart' with optional filtering, which is a specific verb+resource combination. However, it doesn't distinguish this tool from similar sibling tools like 'list_tasks' or 'list_task_comments' beyond mentioning 'docs' specifically.

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 'get_doc' (for single document retrieval) or 'list_tasks' (for different resource types). It mentions filtering capabilities but doesn't explain when filtering is appropriate or when other tools might be better suited.

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

Related 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/its-dart/dart-mcp-server'

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