Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

dramabox_suggest

Retrieves DramaBox autocomplete suggestions for a partial search keyword, returning matching book and performer rows with public catalog metadata.

Instructions

Get DramaBox search-box suggestions. Returns the DramaBox Android app API's autocomplete suggestions for a partial query: book rows (kind "book", cover_url) and performer rows (kind "actor", avatar, series count). The keyword is trimmed and truncated to 80 characters like the app; a query with no match returns an empty items list. Only public catalog metadata is read; no playable video is returned.

Input Schema

NameRequiredDescriptionDefault
keywordYesPartial search text, trimmed and truncated to 80 characters

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.16

TDQS

A3.7/5.0
Behavior4/5

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

With no annotations, the description carries the full load and does well: it discloses that only public catalog metadata is read, that no playable video is returned, that the keyword is trimmed and truncated to 80 characters, and that a no-match query produces an empty items list. It stops short of stating result-count limits or rate/availability characteristics, which would push it to a 5.

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?

Front-loaded with the purpose, then output shape, then input handling, then a safety note. Four dense sentences with only mild redundancy where the 80-character truncation repeats the schema wording.

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?

No output schema exists, and the description compensates by naming the row kinds and their key fields (cover_url, avatar, series count), plus the empty-result behavior. For a single-parameter autocomplete tool that is close to complete; only the maximum number of returned suggestions is unstated.

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 coverage is 100% and the single parameter is already documented as "trimmed and truncated to 80 characters". The description restates the same truncation rule and adds the note it mimics the app's behavior, but contributes no new syntax, format, or edge-case semantics beyond the schema.

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?

A specific verb plus resource ("Get DramaBox search-box suggestions") and an explicit statement that it returns autocomplete for a partial query. The distinction from dramabox_search is implied by the word "autocomplete" but no sibling is named, so the separation still requires the agent to infer it.

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

Usage Guidelines3/5

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

The typeahead framing implies the when (partial query, search-box style), but there is no explicit when-to-use / when-not guidance and no reference to dramabox_search or dramabox_browse as the alternative for full-result lookups. The agent must infer routing from the word "suggestions" alone.

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

Deploy Server

Other Tools