Skip to main content
Glama
Sign In

Crawlora MCP

by net.crawlora
OverviewDiscussionsAdmin

webtoon_originals

Read-only

List one day of WEBTOON's Originals release calendar: every series updating on that weekday (or the complete tab for finished series), with each series' title_no, title, genre, authors, thumbnail, canonical URL, WEBTOON's own counter and UP badge. Use this to track release schedules; there is no paging because the whole day is one page.

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": {
      "day": "<day>"
    },
    "name": "webtoon_originals"
  }
}

Input Schema

NameRequiredDescriptionDefault
dayYesRequired release day, one of: monday, tuesday, wednesday, thursday, friday, saturday, sunday, complete (finished series).
sortNoResult ordering, one of: MANA, LIKEIT, UPDATE. Defaults to MANA.

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 and openWorldHint, so the safety profile is covered. The description's genuinely additive detail is "there is no paging because the whole day is one page," which tells the agent not to expect or request pagination. The enumerated return fields are largely redundant with the output schema, so the net behavioral contribution is modest.

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 scope before the use case, and the closing pagination note is a useful non-obvious fact rather than filler. The long embedded field list in sentence one is the only drag on tightness.

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 two-parameter read tool with a full schema and an output schema, the description covers scope, the special day value, and pagination expectations. The field enumeration is slightly redundant given the output schema, but nothing an agent needs to call it correctly is missing.

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 schema already spells out all eight day values including "complete (finished series)" and the sort options with the MANA default. The description reinforces the complete-tab meaning but adds no syntax, format, or interaction detail beyond that; the sort parameter is not addressed at all in the description.

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 one day of WEBTOON's Originals release calendar" gives a specific verb plus a tightly scoped resource, and the parenthetical "(or the complete tab for finished series)" resolves the one ambiguity in scope. An agent can tell this apart from a genre browser, a rankings list, or a search tool without opening any schema.

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 track release schedules" supplies a clear intended context, and the day-scoped framing implicitly excludes keyword or genre lookups. No explicit when-not condition or named alternative is given, so it stops short of a 5.

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