Skip to main content
Glama
Sign In
Quasar Store Docs MCP

Quasar Store Docs MCP

by iiamdark
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

read_doc

Retrieve the complete content of any Quasar Store documentation article by providing its URL or relative path.

Instructions

Read the full content of a Quasar Store documentation article by its URL or relative path

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": {
      "url": "<url>"
    },
    "name": "read_doc"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesFull article URL or relative path (e.g. "advanced-inventory/installation" or "https://www.quasar-store.com/docs/advanced-inventory/installation")

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.2

TDQS

A4.3/5.0
Behavior4/5

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

For a read-only operation with no annotations, the description transparently indicates it retrieves full content. No side effects or behavioral nuances beyond reading are expected.

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?

Single sentence, no wasted words, clearly front-loaded with the action and object.

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?

Complete for a simple read tool with one parameter and no output schema; no further information is needed for correct usage.

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?

With 100% schema coverage, the description reinforces the parameter's flexibility (URL or path) and adds the return value nature ('full content'), going slightly beyond the schema.

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?

Clearly states the tool reads the full content of a documentation article using a URL or relative path. Distinct from sibling tools list_docs and search_docs which list and search respectively.

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?

Comments imply use when a specific article URL is available, but no explicit when-to-use or when-not-to-use guidance, nor comparisons to alternatives.

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