Skip to main content
Glama
Sign In
Docs Navigator MCP - SUSE Edition

Docs Navigator MCP - SUSE Edition

by mso-docs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

ask_question

Ask a question about SUSE, Rancher, or K3s documentation and get an answer with cited sources.

Instructions

Ask a question about SUSE documentation. The AI will search relevant docs and provide an answer with sources.

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": {
      "question": "<question>"
    },
    "name": "ask_question"
  }
}

Input Schema

NameRequiredDescriptionDefault
contextNoOptional: Additional context or specific area to focus on
questionYesThe question to answer about SUSE/Rancher/K3s documentation

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It discloses that the tool searches docs and returns an answer with sources, but does not explicitly state that it is a read-only operation or describe limitations such as what happens if no relevant documentation is found. The behavior is partially transparent but lacks depth.

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 two sentences long, front-loaded with the core action, and contains no extraneous information. Every word earns its place.

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?

For a simple tool with no output schema, the description adequately explains the result (an answer with sources). It is missing an explicit statement about how it handles out-of-scope questions, but overall it is complete enough for straightforward use.

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 already provides complete descriptions for both parameters ('question' and 'context'). The description adds no additional semantic value for parameters, so the baseline of 3 applies.

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 tool's purpose: asking a question about SUSE documentation and returning an answer with sources. It distinguishes itself from siblings like search_docs (which likely returns raw search results) and summarize_doc (which summarizes content) by emphasizing AI-synthesized answers.

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?

No explicit guidance is given on when to use this tool versus alternatives like search_docs or get_doc_section. The description implies it is for question-answering, but there is no mention of exclusions or when another tool would be more appropriate.

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