Skip to main content
Glama
Sign In

StreamPick

by io.streampick
OverviewDiscussionsAdmin

New on Korean OTT this month

new_releases
Read-only

Movies, series and new seasons released in South Korea in a given month, with the release date and the OTT services they are on. Covers the current month, past months back to 2026-10, and up to two months ahead.

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": "new_releases"
  }
}

Input Schema

NameRequiredDescriptionDefault
sortNodate (default) or buzz for the most talked-about first
limitNoDefault 30, max 100
monthNoYYYY-MM in Korean time. Default: the current month
platformNoOnly titles on this service. One of: netflix, disney_plus, tving, wavve, coupang_play, apple_tv_plus, watcha, amazon_prime

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare a read-only, closed-world operation, so the description only needs to add range behavior — and it does, by naming the exact coverage window (back to 2026-10, two months forward). It also discloses the shape of a result (release date plus OTT services), though it does not mention pagination or what happens for out-of-window months.

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 filler, and the payload description is front-loaded ahead of the coverage-window constraint. Nothing is repeated from the schema and nothing could be cut without losing information.

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 four optional parameters and no output schema, the definition should say what comes back — it does, listing release date and OTT services — and it bounds the valid time range. It stops slightly short on result volume behavior (default 30, max 100 lives only in the schema), which keeps it from a 5.

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% — defaults for month, limit and sort, and the platform enum, are all documented in the schema. The description adds no parameter-level meaning beyond that, so the baseline 3 is appropriate.

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?

The description states a concrete verb-and-resource pair: movies, series and new seasons released in South Korea in a given month, plus the returned fields (release date, OTT services). It is unambiguous about scope, but it never names a sibling such as trending or where_to_watch, so differentiation is left implicit.

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 month-window note ('current month, past months back to 2026-10, up to two months ahead') implicitly tells the agent when this tool is applicable. However, there is no explicit when-not guidance and no pointer to an alternative for title lookups, buzz ranking or service research.

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

All StreamPick 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