Skip to main content
Glama
Kapeli

Dash MCP Server

by Kapeli
OverviewSchemaRelated ServersScoreDiscussions
Python
Local

list_installed_docsets

Lists installed documentation sets in Dash to help users identify available resources for reference and search.

Instructions

List all installed documentation sets in Dash. An empty list is returned if the user has no docsets installed. Results are automatically truncated if they would exceed 25,000 tokens.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
errorNoError message if there was an issue
docsetsNoList of installed docsets

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed8 schema fields changedv1.0.0
    • removedOutput schema / $defs / DocsetInfo
      Removed value: -{
-  "description": "Information about a docset.",
-  "properties": {
-    "full_text_search": {
-      "description": "Full-text search status: 'not supported', 'disabled', 'indexing', or 'enabled'",
-      "title": "Full Text Search",
-      "type": "string"
-    },
-    "identifier": {
-      "description": "Unique identifier",
-      "title": "Identifier",
-      "type": "string"
-    },
-    "name": {
-      "description": "Display name of the docset",
-      "title": "Name",
-      "type": "string"
-    },
-    "notice": {
-      "anyOf": [
-        {
-          "type": "string"
-        },
-        {
-          "type": "null"
-        }
-      ],
-      "default": null,
-      "description": "Optional notice about the docset status",
-      "title": "Notice"
-    },
-    "platform": {
-      "description": "Platform/type of the docset",
-      "title": "Platform",
-      "type": "string"
-    }
-  },
-  "required": [
-    "name",
-    "identifier",
-    "platform",
-    "full_text_search"
-  ],
-  "title": "DocsetInfo",
-  "type": "object"
-}
    • addedOutput schema / $defs / DocsetResult
      Added value: +{
+  "description": "Information about a docset.",
+  "properties": {
+    "full_text_search": {
+      "description": "Full-text search status: 'not supported', 'disabled', 'indexing', or 'enabled'",
+      "title": "Full Text Search",
+      "type": "string"
+    },
+    "identifier": {
+      "description": "Unique identifier",
+      "title": "Identifier",
+      "type": "string"
+    },
+    "name": {
+      "description": "Display name of the docset",
+      "title": "Name",
+      "type": "string"
+    },
+    "notice": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "default": null,
+      "description": "Optional notice about the docset status",
+      "title": "Notice"
+    },
+    "platform": {
+      "description": "Platform/type of the docset",
+      "title": "Platform",
+      "type": "string"
+    }
+  },
+  "required": [
+    "name",
+    "identifier",
+    "platform",
+    "full_text_search"
+  ],
+  "title": "DocsetResult",
+  "type": "object"
+}
    • addedOutput schema / description
      Added value: +"Result from listing docsets."
    • addedOutput schema / properties / docsets
      Added value: +{
+  "description": "List of installed docsets",
+  "items": {
+    "$ref": "#/$defs/DocsetResult"
+  },
+  "title": "Docsets",
+  "type": "array"
+}
    • addedOutput schema / properties / error
      Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Error message if there was an issue",
+  "title": "Error"
+}
    • removedOutput schema / properties / result
      Removed value: -{
-  "items": {
-    "$ref": "#/$defs/DocsetInfo"
-  },
-  "title": "Result",
-  "type": "array"
-}
    • removedOutput schema / required
      Removed value: -[
-  "result"
-]
    • changedOutput schema / title
      Previous value: -"list_installed_docsetsOutput"New value: +"DocsetResults"
  2. First observed

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations provided, the description carries full burden and adds valuable behavioral context: it discloses that results are automatically truncated if exceeding 25,000 tokens and specifies the return condition for no installed docsets. This goes beyond basic functionality, though it could mention performance or error handling.

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 with the core purpose in the first sentence, followed by two concise sentences adding critical behavioral details. Every sentence earns its place with no waste, making it efficient and well-structured.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's simplicity (0 parameters, output schema exists), the description is largely complete. It covers purpose, edge cases (empty list), and a key limitation (token truncation). With an output schema, it need not explain return values, but could slightly enhance by mentioning format or ordering.

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 with 100% schema description coverage, so the schema already fully documents inputs. The description appropriately does not add parameter details, maintaining focus on behavior. Baseline is 4 for zero parameters, as it avoids unnecessary repetition.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the specific action ('List all installed documentation sets in Dash') and resource ('documentation sets'), distinguishing it from siblings like search_documentation or load_documentation_page. It provides precise scope by specifying 'installed' and the context of Dash.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage for retrieving installed docsets, but does not explicitly state when to use this tool versus alternatives like search_documentation. It mentions an empty list result condition, which gives some context, but lacks explicit guidance on scenarios or prerequisites.

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

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/Kapeli/dash-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server