Crawlora MCP

dramabox_home

Read-only

List DramaBox's featured short dramas and its three curated shelves (Trending, Must-sees, Hidden gems) with each title's id, title, description, cover, link, episode count, tags, genres and displayed view count. Use this to see what DramaBox is promoting. Only public catalog metadata is returned, never playable video.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "dramabox_home"
  }
}

Input Schema

Name	Required	Description	Default
`language`	No	Site locale, one of: en, ko, zhHans, zh, es, ja, de, in, th, tl, pt, fr, ar, it (in is Indonesian); defaults to en. Each locale has its own title library. Documented values: en, ko, zhHans, zh, es, ja, de, in, th, tl, pt, fr, ar, it.

Output Schema

Name	Required	Description	Default
`data`	Yes	The tool result payload (shape varies per tool; see each tool's docs resource).

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 26, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations already supply readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds genuinely useful nuance beyond that: it enumerates exactly what metadata each title carries (id, title, cover, episode count, tags, genres, displayed view count) and rules out an expectation an agent could plausibly have by saying 'never playable video'. Rate limits, pagination and caching are not mentioned.

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

Conciseness4/5

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

Two sentences, front-loaded with the resource and its shelves, followed by the usage cue and one non-obvious constraint. The field enumeration in sentence one is long, but every item is load-bearing information about the payload. Nothing is wasted.

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?

An output schema exists, so the description need not explain return shapes, yet it still summarizes them helpfully. One optional parameter is fully documented in the schema. The only real gap is sibling routing, which matters here given four other dramabox_* tools.

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%: the single optional `language` parameter is fully documented in the schema, including the enumerated locale codes and the en default. The description does not mention language at all, so it adds nothing on top of a schema that already does the job. Baseline 3 is correct here.

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

Purpose4/5

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

States a specific verb and resource: 'List DramaBox's featured short dramas and its three curated shelves', and even names the shelves (Trending, Must-sees, Hidden gems) plus the fields returned. It is easy to picture the payload. What keeps it from a 5 is that it never distinguishes itself from the sibling tools dramabox_browse, dramabox_drama, dramabox_genres and dramabox_more.

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?

'Use this to see what DramaBox is promoting' gives a clear, concrete selection context: promotion/editorial surface rather than search. However, no alternatives or exclusions are stated, so an agent must infer on its own when to reach for dramabox_browse or dramabox_genres instead.

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

All Crawlora MCP tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.