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 across 1 of 1 tools scored.
With only one tool, there is no possibility of confusion between tools. The tool's purpose is clearly described and distinct.
Single tool name 'vozclara_generate_pack' follows a clear verb_noun pattern, consistent within the set.
A single tool feels too thin for a server; typical servers have 3-15 tools. This appears to be a minimal implementation.
The surface is severely incomplete: it only provides generation of knowledge packs, lacking any retrieval, listing, or management tools for the created 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.
| 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 |
| 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?
No annotations are provided, so the description carries full burden. It describes the output structure but omits behavioral details like processing time, error handling for invalid URLs, or rate limits. The description is adequate but not exhaustive.
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 sentences: one for usage trigger, one for output summary. No redundancy, every word serves a purpose. Ideal length for quick understanding.
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?
Given no output schema, the description compensates by listing return fields. It covers the essential purpose, input requirements (though not explicitly repeated), and output structure. Missing details like processing characteristics, but sufficient for basic understanding.
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 each parameter having a clear description. The tool description adds minimal extra value beyond the schema, reinforcing the output format but not detailing parameter usage or constraints.
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?
The description clearly states the tool's purpose: generating a Knowledge Pack from a YouTube video when the user asks for summary or study material. It specifies the output structure (title, summary, key ideas, link), making the function unambiguous.
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 states when to use the tool ('when the user asks for a summary, key ideas, or study material'), providing clear guidance. No alternatives or when-not-to-use cases are given, but no sibling tools exist to confuse selection.
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!