Skip to main content
Glama
Kapeli

Dash MCP Server

by Kapeli
OverviewSchemaRelated ServersScoreDiscussions
Python
Local

search_documentation

Search across documentation sets and code snippets to find relevant information from installed Dash docsets using specific queries.

Instructions

Search for documentation across docset identifiers and snippets.

Args:
    query: The search query string
    docset_identifiers: Comma-separated list of docset identifiers to search in (from list_installed_docsets)
    search_snippets: Whether to include snippets in search results
    max_results: Maximum number of results to return (1-1000)

Results are automatically truncated if they would exceed 25,000 tokens.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYes
docset_identifiersYes
search_snippetsNo
max_resultsNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
errorNoError message if there was an issue
resultsNoList of search results

Schema Changelog

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

  1. Changed14 schema fields changedv1.0.0
    • removedInput schema / properties / docset_identifiers / anyOf
      Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
    • removedInput schema / properties / docset_identifiers / default
      Removed value: -null
    • addedInput schema / properties / docset_identifiers / type
      Added value: +"string"
    • changedInput schema / required
      Previous value: -[
-  "query"
-]New value: +[
+  "query",
+  "docset_identifiers"
+]
    • addedOutput schema / $defs / SearchResult / properties / platform / anyOf
      Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]
    • addedOutput schema / $defs / SearchResult / properties / platform / default
      Added value: +null
    • removedOutput schema / $defs / SearchResult / properties / platform / type
      Removed value: -"string"
    • changedOutput schema / $defs / SearchResult / required
      Previous value: -[
-  "name",
-  "type",
-  "platform",
-  "load_url"
-]New value: +[
+  "name",
+  "type",
+  "load_url"
+]
    • addedOutput schema / description
      Added value: +"Result from searching documentation."
    • 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/SearchResult"
-  },
-  "title": "Result",
-  "type": "array"
-}
    • addedOutput schema / properties / results
      Added value: +{
+  "description": "List of search results",
+  "items": {
+    "$ref": "#/$defs/SearchResult"
+  },
+  "title": "Results",
+  "type": "array"
+}
    • removedOutput schema / required
      Removed value: -[
-  "result"
-]
    • changedOutput schema / title
      Previous value: -"search_documentationOutput"New value: +"SearchResults"
  2. First observed

TDQS

A4.1/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. It discloses key behavioral traits: results are 'automatically truncated if they would exceed 25,000 tokens,' and it explains parameter defaults and constraints (e.g., 'max_results: 1-1000'). However, it doesn't cover aspects like rate limits, authentication needs, 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 appropriately sized and front-loaded: the first sentence states the purpose, followed by a structured list of parameters with clear explanations. Every sentence adds value without redundancy, making it efficient and easy to parse.

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 moderate complexity (4 parameters, no annotations, but with an output schema), the description is mostly complete. It covers purpose, parameters, and key behavior (truncation), but lacks details on output format or error cases, though the output schema may mitigate this. For a search tool, it's reasonably comprehensive.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must compensate fully. It adds significant meaning beyond the schema: it explains that 'docset_identifiers' are 'comma-separated' and sourced 'from list_installed_docsets', clarifies 'search_snippets' as 'whether to include snippets', and specifies 'max_results' range and default. This effectively documents all parameters.

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: 'Search for documentation across docset identifiers and snippets.' It specifies the verb ('search') and resource ('documentation'), but doesn't explicitly differentiate from sibling tools like 'load_documentation_page' or 'list_installed_docsets' beyond mentioning docset identifiers come from the latter.

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 through the mention of 'docset identifiers (from list_installed_docsets)' and the parameter descriptions, but lacks explicit guidance on when to use this tool versus alternatives like 'load_documentation_page' or 'enable_docset_fts'. No exclusions or clear context for tool selection are provided.

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