oratilo-mcp

oratilo_search

Search oratilo video summaries by topic, phrase, person, or company when you lack a specific video URL. Returns ranked matches with page links and snippets to reveal library coverage.

Instructions

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.

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": {
      "query": "<query>"
    },
    "name": "oratilo_search"
  }
}

Input Schema

Name	Required	Description
`lang`	No	Language index to search (default ko)
`limit`	No	Max results, 1–20 (default 8)
`query`	Yes	Search terms. Multiple words are AND-ed.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.0Aug 3, 2026

TDQS

A4/5.0

Behavior3/5

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

With no annotations provided, the description carries the full burden. It discloses that results are ranked matches with page links and snippets, and that it searches across a library index (implying it's read-only). It doesn't disclose pagination behavior, rate limits, or what 'full text search' means regarding partial matches, but the read-only nature is reasonably implied by the search-then-lookup pattern.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, zero wasted words. The first sentence states purpose and when to use, the second describes the return format and follow-up action. Extremely efficient and front-loaded.

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 search tool with no output schema and no annotations, the description is fairly complete: it explains the purpose, return format (ranked matches with page links and snippets), and directs follow-up. It could add what fields each result contains or note that 'full text of one' via lookup implies snippets come first, but it's adequate for a search-with-lookup sibling pattern.

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 description coverage is 100%, so the schema fully documents all three parameters (query, lang, limit). The description mentions searching by topic/phrase/person/company which maps to query usage, and notes the AND-ed multi-word behavior is in the schema. The description adds minor value by framing what query types are useful but doesn't go much beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Description uses a specific verb (Search) with a specific resource (full text of oratilo summaries) and enumerates search dimensions (topic, phrase, person, company). It clearly distinguishes from the sibling tool by explaining when this one is appropriate (when you do not have a specific video URL) and directs follow-up to oratilo_lookup for full text of one result.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description gives clear context on when to use this tool ('when you do not have a specific video URL but want to know what the library covers') and directs users to oratilo_lookup for full text retrieval. However, it doesn't explicitly state when to NOT use this tool or contrast with the sibling for the lookup use case.

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

Deploy Server