Skip to main content
Glama
Sign In

Crawlora MCP

by net.crawlora
OverviewDiscussionsAdmin

twitch_search

Read-only

Search Twitch's capped typeahead surface and return mixed channel and category records, with live viewer counts when available. Use twitch_channel or twitch_streams for channel detail/live status, or twitch_top_games for top categories.

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": {
      "query": "<query>"
    },
    "name": "twitch_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoNumber of results to return (default 10, max 30)
queryYesSearch text (category/game name or channel name)

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 / limit / description
      Added value: +"Number of results to return (default 10, max 30)"
    • addedInput schema / properties / query / description
      Added value: +"Search text (category/game name or channel name)"
  2. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint, openWorldHint), so the description's value-add is elsewhere: it discloses that the surface is 'capped' typeahead (i.e. not an exhaustive search) and that live viewer counts appear only 'when available' — both non-obvious result traits. It stops short of stating the cap value or pagination behavior.

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 with zero filler: the first defines scope and output, the second handles routing. Front-loaded and appropriately sized for a two-parameter search tool.

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

Completeness5/5

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

With an output schema present, return values need not be described in depth, and the description still sketches result composition and the cap. Safety, scope, and sibling routing are all covered, leaving nothing an agent needs 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 100% (query semantics and limit default/max are already documented in the schema), so the baseline is 3. The description adds only an indirect hint about result types, not new query syntax or filtering semantics.

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?

States a specific verb (Search) and resource (Twitch's capped typeahead surface) and explicitly characterizes the return payload as mixed channel and category records. It also names the sibling tools it is not, so an agent can distinguish it without opening another schema.

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

Usage Guidelines5/5

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

The second sentence routes the agent explicitly: use twitch_channel or twitch_streams for channel detail/live status, and twitch_top_games for top categories. The condition selecting each alternative is stated rather than implied.

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