Skip to main content
Glama

doctor

Checks installed versions, optional features, and YouTube reachability so you can diagnose why any TubeLens tool misbehaves; run it first when something fails.

Instructions

Self-check: versions, which optional features are installed, and whether YouTube is reachable. Run this first if any tool misbehaves.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "doctor"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A4.5/5.0
Behavior4/5

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

With no annotations, the description carries the full burden, and it does disclose the diagnostic surface (versions, feature presence, network reachability). 'Self-check' makes the non-mutating nature clear by implication, though it never states outright that it changes nothing or whether the YouTube probe consumes quota.

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?

Two sentences, zero waste. The capability summary is front-loaded and the actionable instruction follows, which is the right ordering for a diagnostic tool.

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?

An output schema exists, so the description need not explain what is returned, and with zero parameters there is no input surface to document. What remains — what it checks and when to invoke it — is fully covered.

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?

The tool takes zero parameters, so per the baseline there is nothing for the description to disambiguate. No parameter text is needed and none is misleadingly absent.

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 gives a specific verb ('Self-check') and enumerates exactly what is inspected: versions, installed optional features, and YouTube reachability. It is unmistakably distinct from the sibling tools, which are all content-retrieval/enrichment tools, so an agent can pick it without inspecting any schema.

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?

It supplies a concrete trigger condition: 'Run this first if any tool misbehaves.' That is actionable routing guidance rather than an implied use. It stops short of an explicit when-not-to-use or a named alternative, which is what a 5 would require.

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