Skip to main content
Glama
mamit514

quasar-docs-mcp-server

by mamit514

quasar_list_sections

List all Quasar documentation sections or view pages within a specific section. Navigate and explore the docs structure.

Instructions

List all available Quasar documentation sections, or list pages within a specific section.

Use this to discover what documentation is available and navigate the docs structure.

Args:

  • section (string, optional): Show pages within a specific section (e.g., 'vue-components')

  • response_format ('markdown' | 'json'): Output format (default: 'markdown')

Returns: When listing all sections (no section parameter): For markdown: Formatted list of sections with titles, descriptions, and page counts For JSON: { "total_sections": number, "sections": [ { "name": string, // Section identifier (e.g., 'vue-components') "path": string, // URL path "title": string, // Human-readable title "description": string, // Section description "page_count": number // Number of pages in section } ] }

When listing pages in a section: For markdown: List of pages with titles and paths For JSON: { "section": string, "total_pages": number, "pages": [ { "title": string, "path": string, "url": string } ] }

Examples:

  • List all sections: (no parameters)

  • List component pages: section="vue-components"

  • List plugins: section="quasar-plugins"

  • Get JSON format: section="style", response_format="json"

Errors:

  • Returns available sections if specified section doesn't exist

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sectionNoOptional: show pages within a specific section (e.g., 'vue-components')
response_formatNoOutput format: 'markdown' for human-readable or 'json' for machine-readablemarkdown
Behavior5/5

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

With no annotations, the description fully discloses behavior: it details two distinct modes (listing sections vs. listing pages), specifies return formats (markdown and JSON), and explains error behavior (returns available sections on invalid section name).

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

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

The description is well-organized with clear sections (Args, Returns, Examples, Errors) and is front-loaded with the main purpose. While slightly verbose, every sentence serves a purpose.

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

Completeness5/5

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

For a tool with no output schema, it thoroughly documents both markdown and JSON return structures for both usage modes. It covers all parameters, provides multiple examples, and addresses error handling. No gaps remain.

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?

Although schema coverage is 100%, the description adds value by explaining each parameter's role with examples and default values. It clarifies how section works as an optional filter and describes response_format with enum options.

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 it lists all Quasar documentation sections or pages within a section. It distinguishes from siblings (quasar_get_component, quasar_get_page, quasar_search_docs) by focusing on navigation and discovery rather than retrieving specific content.

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

Usage Guidelines5/5

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

The description explicitly says 'Use this to discover what documentation is available and navigate the docs structure.' It provides concrete examples for listing all sections, listing pages in a section, and even error handling when a specified section doesn't exist.

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/mamit514/quasar-docs-mcp-server'

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