Skip to main content
Glama
its-dart

Dart MCP Server

by its-dart

get_view

Retrieve a specific view by its ID from Dart MCP Server to access detailed information, including title, description, and associated tasks.

Instructions

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

Input Schema

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

Implementation Reference

  • Handler for the 'get_view' tool: validates the 12-character ID argument and fetches the view data using ViewService.getView(id), then returns it as JSON string.
    case GET_VIEW_TOOL.name: {
      const id = getIdValidated(args.id);
      const view = await ViewService.getView(id);
      return {
        content: [{ type: "text", text: JSON.stringify(view, null, 2) }],
      };
    }
  • Schema definition for the 'get_view' tool, specifying the name, description, and input schema that requires a single 'id' property matching the 12-character alphanumeric pattern.
    export const GET_VIEW_TOOL: Tool = {
      name: "get_view",
      description:
        "Retrieve an existing view by its ID. Returns the view's information including title, description, and all tasks within it.",
      inputSchema: {
        type: "object",
        properties: {
          id: {
            type: "string",
            description: "The 12-character alphanumeric ID of the view",
            pattern: "^[a-zA-Z0-9]{12}$",
          },
        },
        required: ["id"],
      },
    };
  • index.ts:192-214 (registration)
    Registration of the 'get_view' tool (as GET_VIEW_TOOL) in the TOOLS array, which is served via ListToolsRequestSchema to make the tool available to the MCP client.
    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)
    Server request handler for listing tools, returning the TOOLS array that includes 'get_view'.
    server.setRequestHandler(ListToolsRequestSchema, async () => ({
      tools: TOOLS,
    }));
Behavior3/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. It discloses that the tool retrieves by ID and returns view information including title, description, and tasks, which adds useful behavioral context beyond the schema. However, it doesn't cover aspects like error handling, permissions, or rate limits, leaving gaps for a tool with no annotations.

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?

The description is front-loaded and efficient: two sentences that directly state the action and return value without waste. Every sentence earns its place by conveying essential information clearly and succinctly.

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 minimally adequate. It explains what the tool does and what it returns, but lacks details on error cases, permissions, or integration with siblings. Without annotations or output schema, more context would improve completeness for safe agent use.

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 input schema has 100% description coverage, documenting the ID parameter's format and requirement. The description adds no additional parameter semantics beyond what the schema provides (e.g., no examples or edge cases). According to the rules, with high schema coverage, the baseline is 3 even with no param info in the description.

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 view by its ID' specifies the verb (retrieve) and resource (view). It distinguishes from siblings like get_task or get_doc by focusing on views, though it doesn't explicitly contrast with them. The description is specific but lacks explicit sibling differentiation.

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 when to use get_view over other get_* tools (e.g., get_task, get_doc) or list_tasks, nor does it specify prerequisites or exclusions. Usage is implied by the purpose 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