Skip to main content
Glama

recent_streams

Read-only

最近の歌唱パフォーマンスを新しい順に一覧する(キーワード不要)。since/until で期間、singerId で歌い手を絞り込める。日時は ISO 8601 形式のみ(例: 2026-07-01 / 2026-07-01T12:00:00+09:00)。タイムゾーンオフセットのない日時は日本時間(JST)として解釈される。YYYY-MM-DD は since ではその日の JST 0時、until ではその日の終わり(当日を含む)として解釈される。「今週配信された歌唱」「この歌い手の直近の活動」に答える用途。

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

Input Schema

NameRequiredDescriptionDefault
limitNo
sinceNo
untilNo
contextNoこのツールを呼ぶ目的やユーザーの依頼の要約(1文・任意)。検索品質の改善のためのログに記録されます
singerIdNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare readOnly/non-destructive/closed-world, and the description adds real behavior beyond them: default newest-first ordering, JST defaulting for offset-less timestamps, and inclusive end-of-day for date-only until. It says nothing about the default page size, whether limit is capped/paginated, or what the response contains.

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?

Front-loaded with the core action, then filters, then the exact date/time interpretation rules and worked examples, then use cases. Every sentence carries semantics an agent would otherwise have to guess; nothing is repeated from the schema.

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 5-parameter read tool with no output schema and only minimal annotation burden, the time-window semantics are documented in unusual depth. The remaining gap is paging behavior: the description never states the default limit or what happens past 50 results.

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 only 20%, but the description compensates heavily for the hardest parameters: ISO 8601 format, max/min length intent, timezone fallback, and the since/until boundary semantics. limit is never mentioned (no default, no cap explanation) and singerId is named without any format or sourcing guidance, so coverage is uneven rather than complete.

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?

Specific verb + resource: lists recent singing performances, newest first, and explicitly notes no keyword is needed, which distinguishes it from keyword-based search siblings. The scope statement is precise enough that an agent can pick this tool without opening a 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?

Gives concrete user-question triggers ('what was streamed this week', 'this singer's recent activity') and says keywordless lookup is the point. It stops short of naming when to prefer a sibling such as list_singer_performances for deep historical per-singer listing, so the boundary is implied rather than stated.

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