Skip to main content
Glama

配信予告の条件検索

search_live_streams
Read-onlyIdempotent

配信予定をJSTの日付・時間帯・初配信候補・ジャンルで検索。公開アクセスでは最大7日間・10件。通常・デビューとも現行予告のみ。開始予定時刻を過ぎた予告は猶予期間後に対象外。過去のデビュー予告・終了済み配信の履歴は取得不可。総一致件数も返す。

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

Input Schema

NameRequiredDescriptionDefault
limitNo
date_toNo
keywordNo
categoryNo
end_timeNo
date_fromNo
debut_onlyNo
start_timeNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior5/5

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

Beyond the annotations, which already declare a safe, idempotent, closed-world read, the description discloses the retention window (7 days, 10 items for public access), the grace-period expiry rule, the fact that only current schedules are covered for both normal and debut entries, and that historical data is unavailable. It also states that a total match count is returned, which is behavioral information not derivable from the schema.

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?

Six short, dense clauses with the search scope front-loaded and each subsequent sentence adding a distinct constraint (window, expiry, excluded history, return count). Nothing is redundant and nothing repeats the schema or annotations.

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 an 8-parameter, no-output-schema search tool with annotations already covering safety, the description covers scope, limits, expiry, exclusions, and the aggregate count return. It falls short only on keyword semantics, limit behavior versus the stated 10-item cap, and the accepted date/time string format, which the agent needs in order to call it correctly.

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 0%, so the description must carry parameter meaning, and it does map most filters: date range, start/end time band, debut_only, and category. However, 'keyword' and 'limit' go unmentioned (the '10 items' cap only hints at the limit ceiling), and neither the date/time string format nor how the time band interacts with the date range is explained.

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 opening clause names a specific verb and resource plus the four filter axes (JST date, time band, debut candidate, genre), so an agent immediately knows this is a conditional search over scheduled (future) streams rather than current or past ones. It does not name the sibling search_current_live_streams explicitly, which is the one remaining differentiating gap.

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?

The description gives concrete when-not conditions: schedules past their start time drop out after a grace period, past debut schedules and ended-stream history cannot be retrieved, and public access is bounded to 7 days and 10 results. It stops short of pointing to an alternative tool for the excluded cases (e.g., current or past streams), so routing is implied rather than prescribed.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources