Skip to main content
Glama
tubearchivist-mcp

tubearchivist-mcp

by si-essence

ta_system

Read-only

Check Tube Archivist server availability with ping and health probes, or read in-app notifications to monitor system status.

Instructions

Ping, health, and in-app notification messages. Reads only. Actions: ping (GET /api/ping/), health (GET /api/health/), notifications (GET /api/notification/).

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": {
      "action": "<action>"
    },
    "name": "ta_system"
  }
}

Input Schema

NameRequiredDescriptionDefault
actionYesTube Archivist operation to call.
filterNofilter

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=true, so the 'Reads only' sentence mostly restates structured data. The endpoint mapping adds genuine context about what each action hits, but nothing is said about response shape, pagination, or failure behavior for health checks.

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?

Three short, front-loaded clauses with no filler; the action-to-endpoint mapping is compact and scannable. The opening noun list is slightly awkward compared to a verb-first statement but costs almost nothing.

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 small read-only multiplexer with a fully described two-parameter schema and no output schema, the definition covers the operations and endpoints adequately. The remaining gap is the unspecified filter parameter and what ping/health actually return.

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%, so baseline is 3. The description usefully clarifies what each enum value of 'action' does, but it says nothing about 'filter' — whose schema description is merely the word 'filter' — leaving its semantics and which actions it applies to unexplained.

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 the three concrete operations (ping, health, notifications) and maps each to its backend endpoint, so an agent knows exactly what the tool covers. It does not distinguish itself from siblings such as ta_notify, which an agent might reasonably confuse with the notifications action.

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?

The phrase 'Reads only' implies a safe, non-mutating use case, but there is no explicit when-to-use guidance, no statement of when to prefer a sibling, and no mention of when the filter parameter is relevant (presumably only for notifications).

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