vozclara
Server Details
Multilingual YouTube → Knowledge Pack engine. Paste a video URL and get a structured pack — summary, key ideas, glossary, quiz, transcript with timestamps — in Spanish, Portuguese, German, or English. Anonymous endpoint plus OAuth-gated tools for library search, RAG Q&A on a single pack, and Anki export.
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
Glama MCP Gateway
Connect through Glama MCP Gateway for full control over tool access and complete visibility into every call.
Full call logging
Every tool call is logged with complete inputs and outputs, so you can debug issues and audit what your agents are doing.
Tool access control
Enable or disable individual tools per connector, so you decide what your agents can and cannot do.
Managed credentials
Glama handles OAuth flows, token storage, and automatic rotation, so credentials never expire on your clients.
Usage analytics
See which tools your agents call, how often, and when, so you can understand usage patterns and catch anomalies.
Tool Definition Quality
Average 4.5/5 across 1 of 1 tools scored.
Only one tool exists, so there is no possibility of confusion between tools.
With a single tool, naming consistency is inherently maintained. The tool name 'vozclara_generate_pack' follows a clear verb_noun pattern.
The server has only one tool, which is very thin for typical usage. Users likely need additional operations like listing or deleting packs, making the tool count feel insufficient.
The tool only supports creating a knowledge pack. Missing operations such as retrieval, listing, or deletion leave significant gaps in the expected lifecycle for managing packs.
Available Tools
1 toolvozclara_generate_packGenerate a Knowledge Pack from a YouTube videoAInspect
Use this when the user asks for a summary, key ideas, or study material from a YouTube video. Returns a structured Knowledge Pack: title, short summary, key ideas, and a link to the full pack on vozclara.app. Pass format="obsidian" to get vault-ready Markdown with YAML frontmatter the user can save to their second brain.
| Name | Required | Description | Default |
|---|---|---|---|
| url | Yes | Public YouTube video URL (youtube.com/watch?v=… or youtu.be/… short form). | |
| depth | No | Depth of the generated pack. `short` = one-paragraph summary. `standard` = summary + 3-5 key ideas. `deep` = summary + key ideas + glossary + quiz. | standard |
| format | No | Output format. `standard` = plain prose for chat. `obsidian` = Markdown with YAML frontmatter (source, videoId, languages, tags) ready to write straight into an Obsidian vault or any Markdown knowledge base. Use `obsidian` when the user asks to save the pack to their vault / second brain / notes. | standard |
| language | Yes | Output language for the Knowledge Pack: es (Spanish), pt (Portuguese), de (German), en (English). |
Tool Definition Quality
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Describes what the tool returns (title, summary, key ideas, link) and format options (standard vs obsidian with YAML). No annotations provided, so description carries full burden; it is sufficient but does not mention potential limitations or prerequisites beyond what is in schema.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two concise, front-loaded sentences that immediately convey usage context and core functionality. No redundant or extraneous information.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
No output schema or sibling tools exist; description provides sufficient detail on return structure and format choices. Covers key aspects for agent decision-making without omissions.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100% with clear descriptions for each parameter. Description adds value by explaining when to use the 'obsidian' format and implicitly associating 'depth' values with output characteristics.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
Description clearly states the tool generates a Knowledge Pack from a YouTube video, listing output components. No sibling tools exist, so differentiation is not needed.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Explicitly says when to use (user asks for summary, key ideas, study material). Provides guidance on format choice ('obsidian' for saving to vault). No exclusion or alternative mention, but adequate given no sibling tools.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Claim this connector by publishing a /.well-known/glama.json file on your server's domain with the following structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"maintainers": [{ "email": "your-email@example.com" }]
}The email address must match the email associated with your Glama account. Once published, Glama will automatically detect and verify the file within a few minutes.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
Discussions
No comments yet. Be the first to start the discussion!