Skip to main content
Glama
Fetchproof MCP Server

Fetchproof MCP Server

twitch_user_schedule

Retrieve a Twitch user's schedule by handle to view upcoming streams and plan around their broadcast times.

Instructions

twitch: User Schedule. GET /v1/twitch/user/schedule. Get Twitch user schedule Costs 1 credit when it succeeds. Errors, blocked or timed-out requests, invalid requests and cache hits cost nothing. A not-found or empty result is charged only where that operation's published cost says so.

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": {
      "handle": "<handle>"
    },
    "name": "twitch_user_schedule"
  }
}

Input Schema

NameRequiredDescriptionDefault
handleYesTwitch handle

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.8/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden; it does disclose a concrete billing behavior (1 credit on success, free for errors, blocked, timed-out, invalid requests and cache hits) which is genuinely useful context beyond structured fields. However, it omits other behavioral traits an unannotated read tool should cover, such as whether the response is paginated, what a not-found response looks like, or any auth requirements, and the final sentence about not-found charging is vague boilerplate.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The opening is front-loaded with name, route, and purpose, which is good. But the trailing cost paragraph is repetitive boilerplate ("Errors, blocked or timed-out requests, invalid requests and cache hits cost nothing") and its last sentence about not-found charging is convoluted relative to the value it delivers.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema and no annotations, the description should clarify what a user schedule returns and how to interpret an empty result, but it only covers billing. For a simple one-parameter read endpoint it is minimally adequate, though an agent still cannot anticipate the response shape.

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?

The single parameter has 100% schema description coverage ("Twitch handle" with example "nasa"), so the schema already does the work and the baseline is 3. The description adds no additional meaning about the handle format, lookup semantics, or case sensitivity.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description says "Get Twitch user schedule" and repeats the HTTP route GET /v1/twitch/user/schedule, which conveys the verb and resource but largely restates the tool name. It gives no differentiation from sibling tools like twitch_user_clips, twitch_user_videos, or twitch_profile, so an agent cannot tell from this text alone what distinct data a schedule returns versus other Twitch user endpoints.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no statement of when to use this tool versus the other Twitch user tools, no prerequisites, and no exclusions. The only guidance-like content is the cost model, which says nothing about selection between alternatives.

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

Deploy Server

Other Tools