Skip to main content
Glama
Sign In
Dart MCP Server

Dart MCP Server

by jmanhype
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Hybrid

get_dartboards

Retrieve available dartboards from a specified space using the space DUID to organize and manage workspace resources.

Instructions

Get available dartboards

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "space_duid": "<space_duid>"
    },
    "name": "get_dartboards"
  }
}

Input Schema

NameRequiredDescriptionDefault
space_duidYesSpace DUID to get dartboards from

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
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. 'Get available dartboards' implies a read-only operation, but it doesn't specify what 'available' means (e.g., accessible vs. all), whether it requires authentication, rate limits, pagination, or the return format. This leaves significant gaps 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 a single, efficient sentence with zero waste. It's front-loaded with the core action and resource, making it easy to parse quickly. Every word earns its place without redundancy.

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?

Given the complexity (a read operation with one required parameter), no annotations, and no output schema, the description is incomplete. It doesn't explain what 'available' entails, the return structure, or error conditions. For a tool with minimal structured data, more context is needed to guide the agent effectively.

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 schema description coverage is 100%, with the single parameter 'space_duid' documented as 'Space DUID to get dartboards from'. The description adds no additional parameter semantics beyond implying that dartboards are retrieved from a space. Since the schema does the heavy lifting, the baseline score of 3 is appropriate.

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 'Get available dartboards' clearly states the verb 'Get' and resource 'dartboards', making the purpose understandable. However, it doesn't distinguish this tool from potential siblings like 'get_folders' or 'get_default_space' beyond the resource name, and the term 'available' adds some specificity but could be more precise.

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 (e.g., needing a space DUID), exclusions, or how it differs from other 'get' tools in the sibling list. The agent must infer usage from the parameter alone.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools