Skip to main content
Glama

Who is streaming GTA right now

live_gta_streams
Read-onlyIdempotent

Twitch and Kick channels streaming GTA (GTA VI and GTA V) right now, by viewers, each with a heistclips link to find its moments.

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

Input Schema

NameRequiredDescriptionDefault
limitNoHow many (default 15)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

The annotations already establish that this is a safe, read-only, idempotent, non-destructive, open-world lookup. Beyond that, the description adds useful behavioral detail: sources are Twitch and Kick, supported games are GTA VI and GTA V, results are ordered by viewers, and each entry includes a heistclips link.

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?

The definition is a single tightly packed sentence with no redundant wording. It front-loads the core purpose and then adds the most useful distinguishing details: sources, games, ordering, and included link.

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 simple one-parameter read-only listing tool, the description provides enough context to call it correctly and understand the general result shape. It could be slightly more complete about the precise fields returned, but the absence of an output schema is partly offset by the stated viewer ordering and per-channel heistclips link.

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?

There is only one parameter, limit, and the schema fully documents its type, range, default, and meaning. The description adds no further parameter semantics, which is appropriate for a high-coverage one-parameter schema but limits the score to the baseline.

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?

The description names a specific resource and scope: Twitch and Kick channels currently streaming GTA VI or GTA V, ordered by viewers. It clearly distinguishes this live-stream listing from campaign-, moment-, and feature-request-oriented siblings.

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 title and description make the use case clear: retrieve currently live GTA streams. It does not explicitly state when to avoid this tool or name an alternative, but the live-only context is unambiguous and the listed siblings do not appear to overlap.

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.