Skip to main content
Glama

QDev

Get one page or post

get_document
Read-onlyIdempotent

One page or blog post of quantumdev.io as markdown, with its title, address and date. Pages include the home page (what QDev is and its products), the privacy policy and the terms.

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": {
      "id": "<id>"
    },
    "name": "get_document"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesThe document's id from list_documents or search (page:/privacy/, post:<slug>), or its address on quantumdev.io.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so safety is covered. The description adds value the annotations do not: the return format (markdown) and the included metadata (title, address, date), which matters because there is no output schema.

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?

Two short sentences, front-loaded with the core behavior; the second sentence scopes which documents exist, which is genuinely useful rather than padding. Slight trimmability in the parenthetical about QDev products, but nothing wasteful.

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 one-parameter read tool with full schema coverage and rich annotations, the description covers purpose, return format, and document scope. Only the explicit routing to list_documents/search is missing.

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?

Schema coverage is 100% and the single parameter already documents the accepted id forms (page:/privacy/, post:<slug>, or an address), so the description does not need to repeat them. Baseline 3 applies since the schema carries the parameter meaning.

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?

Names a specific resource and verb form: 'One page or blog post of quantumdev.io as markdown, with its title, address and date.' An agent can tell this returns a single document rather than a list, though the description never names the sibling tools (list_documents, search) it complements.

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?

Usage is only implied — it is the single-document counterpart to listing/searching, but the description never says 'use when you already have an id' or excludes any case. The pointer to list_documents/search appears only in the schema parameter text, not in the description.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources