Skip to main content
Glama
its-dart

Dart MCP Server

by its-dart

get_config

Retrieve comprehensive configuration details for Dart project management, including available assignees, dartboards, folders, statuses, tags, and custom properties, to facilitate task and document management.

Instructions

Get information about the user's space, including all of the possible values that can be provided to other endpoints. This includes available assignees, dartboards, folders, statuses, tags, priorities, sizes, and all custom property definitions.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Handler logic for the 'get_config' tool. It invokes ConfigService.getConfig() to fetch the configuration and returns it as a formatted JSON string in the tool response.
    case GET_CONFIG_TOOL.name: {
      const config = await ConfigService.getConfig();
      return {
        content: [{ type: "text", text: JSON.stringify(config, null, 2) }],
      };
    }
  • Schema definition for the 'get_config' tool, specifying its name, description, and empty input schema (no parameters required).
    export const GET_CONFIG_TOOL: Tool = {
      name: "get_config",
      description:
        "Get information about the user's space, including all of the possible values that can be provided to other endpoints. This includes available assignees, dartboards, folders, statuses, tags, priorities, sizes, and all custom property definitions.",
      inputSchema: {
        type: "object",
        properties: {},
        required: [],
      },
    };
  • index.ts:192-214 (registration)
    Registration of the 'get_config' tool (as GET_CONFIG_TOOL) in the TOOLS array, which is returned by the listTools endpoint.
    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 describes what data is returned but lacks critical behavioral details: it does not mention whether this is a read-only operation (implied by 'Get' but not explicit), authentication requirements, rate limits, or response format. For a tool with zero annotation coverage, this is a significant gap in transparency.

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 sized and front-loaded: it starts with the core purpose ('Get information about the user's space') and follows with specifics on included data. Both sentences earn their place by clarifying scope, though it could be slightly more structured (e.g., bullet points for the list). No wasted words or redundancy.

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 complexity (configuration retrieval with multiple data types), lack of annotations, and no output schema, the description is moderately complete. It specifies what information is included but misses behavioral context (e.g., safety, format) and does not explain the return structure. This is adequate for a read operation but leaves gaps for an agent to infer usage.

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?

The tool has 0 parameters, and schema description coverage is 100% (empty schema). The description does not need to add parameter semantics, so it appropriately focuses on the tool's purpose and output. Baseline is 4 for zero parameters, as the description compensates by explaining what the tool returns without parameter distractions.

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: 'Get information about the user's space' with a specific list of included data types (assignees, dartboards, folders, etc.). It uses a specific verb ('Get') and resource ('user's space'), but does not explicitly distinguish it from sibling tools like 'get_dartboard' or 'get_folder' that fetch specific resources rather than comprehensive configuration.

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 mentions that the information 'can be provided to other endpoints,' but does not specify scenarios (e.g., for setup, reference, or filtering) or exclusions compared to sibling tools like 'get_dartboard' or 'list_tasks' that might overlap in data retrieval.

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