oratilo-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ORATILO_BASE | No | Base URL to point the server at a localhost origin for development. Any other host is refused and the server falls back to oratilo.com. |
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 | {} |
| prompts | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| oratilo_lookupA | Check whether oratilo (a shared library of concept-structured video summaries) already has a summary for a specific video, BEFORE spending work summarizing it yourself. Returns the full summary plus provenance metadata on a hit. A miss means the video is not covered — summarize it yourself. Accepts YouTube URLs or video ids (arXiv ids reserved for the future). |
| oratilo_searchA | Search the full text of oratilo summaries by topic, phrase, person or company — use when you do not have a specific video URL but want to know what the library covers. Returns ranked matches with page links and snippets; follow up with oratilo_lookup for the full text of one. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| summarize | Summarize a YouTube video — checks the oratilo library first and reuses an existing summary instead of redoing the work. |
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: lookup is for checking a specific video ID/URL for existing coverage, while search is for discovering what content exists by topic when no specific URL is known. The descriptions explicitly clarify when to use each, leaving no ambiguity whatsoever.
Both tools follow a consistent oratilo_ prefix with a clear verb (lookup, search). The pattern is consistent and predictable, though with only two tools the naming convention is minimally demonstrated.
At 2 tools, the surface feels thin for a library with search and retrieval capabilities, though it could be argued these two operations are the core of what's needed. The count is borderline but reasonable given the limited scope described.
Core read operations (lookup and search) are covered, providing a functional surface. However, there are no write/contribution tools (e.g., adding or updating a summary), so the surface covers only the lookup half of the workflow and leaves the 'summarize it yourself' path entirely to the agent.