aws-blackbelt-mcp-server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_seminarsA | Search AWS Black Belt seminars by keyword. Args: ctx: Context to access MCP features query: Search keyword (e.g., "machine learning", "lambda", "s3") sort_order: Sort order by published date - "desc" (newest first) or "asc" (oldest first) limit: Maximum number of results to return (default: 10, max: 50) Returns: List of seminar information including title, date, PDF and YouTube links |
| get_seminar_transcriptA | Get transcript from seminar video. Note: Supported only in Japanese. Args: ctx: Context to access MCP features youtube_url: YouTube video URL language: Language code for transcript (default: "ja" for Japanese) Returns: Seminar transcript |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 2 tools
The two tools have clearly distinct purposes: one searches for seminar metadata, the other retrieves a transcript from a video URL. There is no overlap or ambiguity between them.
Both tool names follow a consistent verb_noun snake_case pattern (search_seminars, get_seminar_transcript). The naming is predictable and clear.
With only two tools, the server feels minimal but not unreasonable for its narrow domain. It is on the thin end of the scale, leaving limited functionality but still a coherent set.
The server covers the core workflow of finding seminars and accessing their transcripts. A minor gap is the lack of a way to list all seminars without a keyword or fetch seminar details directly, but most use cases are met.