Skip to main content
Glama
its-dart

Dart MCP Server

by its-dart

get_folder

Retrieve folder details by ID, including title, description, and contained documents, for efficient project management on the Dart MCP Server.

Instructions

Retrieve an existing folder by its ID. Returns the folder's information including title, description, and all docs within it.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesThe 12-character alphanumeric ID of the folder

Implementation Reference

  • Handler for the 'get_folder' tool. Validates the input 'id' using getIdValidated and calls FolderService.getFolder(id) to fetch the folder details, returning them as JSON-formatted text.
    case GET_FOLDER_TOOL.name: {
      const id = getIdValidated(args.id);
      const folder = await FolderService.getFolder(id);
      return {
        content: [{ type: "text", text: JSON.stringify(folder, null, 2) }],
      };
    }
  • Input schema and metadata definition for the 'get_folder' tool, requiring a folder 'id' matching the 12-character alphanumeric pattern.
    export const GET_FOLDER_TOOL: Tool = {
      name: "get_folder",
      description:
        "Retrieve an existing folder by its ID. Returns the folder's information including title, description, and all docs within it.",
      inputSchema: {
        type: "object",
        properties: {
          id: {
            type: "string",
            description: "The 12-character alphanumeric ID of the folder",
            pattern: "^[a-zA-Z0-9]{12}$",
          },
        },
        required: ["id"],
      },
    };
  • index.ts:192-214 (registration)
    Registration of the 'get_folder' tool (as GET_FOLDER_TOOL) in the TOOLS array, which is exposed via the 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,
    ];
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states this is a retrieval operation, implying it's read-only, but doesn't clarify permissions, error handling, or rate limits. The description adds some context about what information is returned, but lacks details on behavioral traits like whether it's idempotent or if it requires authentication.

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 concise and front-loaded, with two sentences that efficiently convey the purpose and output. There's no wasted text, but it could be slightly more structured by separating usage guidelines or behavioral details into distinct parts.

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?

Given the tool's low complexity (1 parameter, no output schema, no annotations), the description is moderately complete. It covers the basic purpose and output but lacks usage guidelines and behavioral transparency. Without annotations or an output schema, more detail on error cases or return format would improve completeness for this read operation.

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%, with the input schema fully documenting the 'id' parameter (including pattern and type). The description adds minimal value beyond the schema by mentioning 'ID' but doesn't provide additional semantics like examples or edge cases. Baseline score of 3 is appropriate as the schema handles most of the parameter documentation.

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: 'Retrieve an existing folder by its ID' specifies the verb (retrieve) and resource (folder), and 'Returns the folder's information including title, description, and all docs within it' details the output. However, it doesn't explicitly differentiate from sibling tools like 'get_doc' or 'get_view', which also retrieve resources by ID.

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. It doesn't mention sibling tools like 'list_docs' for browsing folders or 'get_doc' for retrieving individual documents, nor does it specify prerequisites such as needing a valid folder ID. Usage is implied but not explicitly stated.

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