Skip to main content
Glama
mamit514

quasar-docs-mcp-server

by mamit514

quasar_get_page

Fetch any Quasar documentation page by path. Supports markdown and JSON output formats.

Instructions

Get any Quasar documentation page by its path.

Use this for non-component documentation like style guides, plugins, CLI docs, getting started guides, etc.

Args:

  • path (string, required): Path to the documentation page. Examples:

    • 'vue-components/btn' - Component docs

    • 'style/color-palette' - Style documentation

    • 'quasar-plugins/notify' - Plugin docs

    • 'quasar-cli-vite/quasar-config-file' - CLI configuration

    • 'start/installation' - Getting started

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

Returns: For markdown: Full page content with documentation For JSON: { "requested_path": string, // Original path input "resolved_path": string, // Actual file path found "url": string, // Quasar.dev URL "content": string, // Page content "truncated": boolean // Whether content was truncated }

Examples:

  • Get color palette: path="style/color-palette"

  • Get notify plugin: path="quasar-plugins/notify"

  • Get CLI config: path="quasar-cli-vite/quasar-config-file"

Errors:

  • Returns "Page not found" with suggestions if path doesn't exist

  • Automatically tries index.md for directory paths

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pathYesPath to the documentation page (e.g., 'vue-components/btn', 'style/color-palette', 'quasar-plugins/notify')
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?

No annotations are provided, so the description carries full burden. It discloses input parameters, return formats (markdown/JSON with structure), error handling ('Page not found' with suggestions), and automatic index.md resolution for directory paths. This fully informs the agent of the tool's behavior.

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-structured with clear sections (Args, Returns, Examples, Errors) and is front-loaded with the main purpose. It could be slightly more concise, but every sentence adds value. The organization aids quick scanning.

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?

Given the tool's simplicity (2 parameters, no output schema), the description is complete. It covers return values, error cases, and examples. No critical information is missing for an agent to correctly invoke the tool.

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?

Schema coverage is 100%, so baseline is 3. The description adds value by providing extensive examples for the 'path' parameter and explains the 'response_format' in detail, including the JSON return structure. This goes beyond the schema's simple type/enum descriptions.

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 retrieves a Quasar documentation page by path. It distinguishes from siblings by specifying 'Use this for non-component documentation like style guides, plugins, CLI docs, getting started guides, etc.' This explicitly contrasts with quasar_get_component, which presumably handles component-specific docs.

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

Usage Guidelines4/5

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

The description provides clear guidance on when to use this tool (non-component docs) and implicitly contrasts with siblings via examples. It does not explicitly state when not to use it or name alternatives, but the context with sibling tool names makes the usage boundaries reasonably clear.

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