Skip to main content
Glama
Sign In

Crawlora MCP

by net.crawlora
OverviewDiscussionsAdmin

dramabox_genres

Read-only

List the genres DramaBox's catalog can be browsed by (Romance, Werewolves, Revenge, Billionaire and more) as ids and names. Use this to find a genre_id for dramabox_browse.

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_genres"
  }
}

Input Schema

NameRequiredDescriptionDefault
languageNoSite 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

NameRequiredDescriptionDefault
dataYesThe tool result payload (shape varies per tool; see each tool's docs resource).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds that entries come back as ids and names and that the ids feed another tool, which is useful context, but it says nothing about ordering, locale-dependent differences, or result size.

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 short sentences, front-loaded with what is returned before the follow-up workflow hint. Every clause carries information, though the example-genre parenthetical is slightly decorative.

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?

With an output schema covering return values, full schema coverage on the one parameter, and annotations covering safety, the description supplies all the selection-critical information. It would be complete at 5 if it noted that the genre list varies by locale.

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% and the single language parameter is fully documented with its value list and default, so the schema carries the burden. The description never references the locale parameter or its effect on the returned genre set, so it adds nothing here; baseline 3 applies.

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?

'List the genres DramaBox's catalog can be browsed by' is a specific verb plus resource, and the parenthetical examples (Romance, Werewolves, Revenge, Billionaire) make the content concrete. The final clause separates it cleanly from dramabox_browse, which consumes the 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?

'Use this to find a genre_id for dramabox_browse' gives an explicit downstream use case and names the alternative. It stops short of stating when not to call it, but the intended role in the workflow is unambiguous.

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

All Crawlora MCP toolsInspect
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.

Resources