Skip to main content
Glama
its-dart

Dart MCP Server

by its-dart

get_dartboard

Retrieve detailed information about a specific dartboard, including its title, description, and associated tasks, by providing its unique 12-character alphanumeric ID.

Instructions

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

Input Schema

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

Implementation Reference

  • Handler for the get_dartboard tool: validates the ID argument, retrieves the dartboard using DartboardService, and returns the JSON-serialized result.
    case GET_DARTBOARD_TOOL.name: {
      const id = getIdValidated(args.id);
      const dartboard = await DartboardService.getDartboard(id);
      return {
        content: [{ type: "text", text: JSON.stringify(dartboard, null, 2) }],
      };
    }
  • Defines the tool's metadata: name, description, and input schema requiring a 12-character alphanumeric 'id'.
    export const GET_DARTBOARD_TOOL: Tool = {
      name: "get_dartboard",
      description:
        "Retrieve an existing dartboard by its ID. Returns the dartboard'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 dartboard",
            pattern: "^[a-zA-Z0-9]{12}$",
          },
        },
        required: ["id"],
      },
    };
  • index.ts:192-214 (registration)
    Registers the get_dartboard tool (as GET_DARTBOARD_TOOL) in the TOOLS array provided to the MCP server's ListToolsRequestHandler.
    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?

With no annotations provided, the description carries the full burden of behavioral disclosure. It states this is a retrieval operation and describes the return content, but it lacks critical details such as error handling (e.g., what happens if the ID is invalid), authentication needs, rate limits, or whether it's a read-only operation. This is a significant gap for a tool with 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.

Conciseness5/5

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

The description is appropriately sized and front-loaded, consisting of two concise sentences that directly state the tool's function and return value without any wasted words. Every sentence earns its place by providing essential information efficiently.

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 (single parameter, no output schema, no annotations), the description is minimally adequate. It covers the basic purpose and return content, but it lacks completeness in areas like error handling, authentication, or comparison to siblings, which would be helpful for an agent to use it correctly in context.

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, clearly documenting the single required parameter 'id' with its format. The description adds no additional parameter semantics beyond what the schema provides, such as examples or context on where to find the ID. This meets the baseline score when schema coverage is high.

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 with a specific verb ('Retrieve') and resource ('an existing dartboard by its ID'), and it distinguishes this from sibling tools like 'get_doc' or 'get_task' by specifying it returns dartboard information including tasks. However, it doesn't explicitly differentiate from all siblings (e.g., 'get_view' might be similar), keeping it from a perfect score.

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 prerequisites, such as needing a valid dartboard ID, or compare it to other retrieval tools like 'get_doc' or 'get_task', leaving the agent to infer usage from context alone.

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