Skip to main content
Glama
Sign In

Crawlora MCP

by net.crawlora
OverviewDiscussionsAdmin

twitch_streams

Read-only

The top currently-live streams for a Twitch game/category, ranked by viewer count.

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": {
      "game": "<game>"
    },
    "name": "twitch_streams"
  }
}

Input Schema

NameRequiredDescriptionDefault
gameYesTwitch game/category slug (the lowercase URL slug from twitch.tv/directory/category/{slug})
limitNoNumber of streams to return (default 20, max 100)

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. Changed2 schema fields changed
    • addedInput schema / properties / game / description
      Added value: +"Twitch game/category slug (the lowercase URL slug from twitch.tv/directory/category/{slug})"
    • addedInput schema / properties / limit / description
      Added value: +"Number of streams to return (default 20, max 100)"
  2. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds the live-only filter and viewer-count ordering, but says nothing about freshness of the data, pagination, or whether ranking is instantaneous - useful context beyond annotations but not rich.

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?

A single sentence with no filler, front-loading the key qualifiers ('top', 'currently-live', 'ranked by viewer count'). Every clause earns its place.

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-only list tool with an output schema that documents return values, the description is nearly sufficient. The only gap is that it gives no reason to prefer this over the sibling live/stream tools, 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 description coverage is 100%: the game slug format and the limit default/max are already fully documented in the schema. The description only echoes the 'game/category' concept and adds no syntax or format detail beyond it, so baseline 3 applies.

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?

States a specific verb+resource combination ('top currently-live streams for a Twitch game/category') plus a ranking rule ('ranked by viewer count'), which is far more precise than the name alone. It does not name or contrast with siblings like twitch_search or twitch_channel, so an agent must infer the boundary itself.

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?

Usage is only implied: the phrasing suggests 'use this to see the most-watched live streams in a category.' There is no explicit when-to-use, when-not-to-use, or pointer to an alternative such as twitch_search for non-ranked lookups, so routing depends on inference.

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