Skip to main content
Glama

FoxAPIs data sources

Twitch channel

twitch_channel
Read-onlyIdempotent

A Twitch channel: followers, partner status, whether it is live, and its latest video, from the channel name. Costs 2 credits a call; an answer with no data is not charged. Needs your FoxAPIs key (free to start).

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": {
      "channel": "<channel>"
    },
    "name": "twitch_channel"
  }
}

Input Schema

NameRequiredDescriptionDefault
channelYesFor example: "twitch"

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, open-world), so the bar is lower, and the description still adds real value beyond them: a cost of 2 credits per call, a no-charge guarantee when an answer has no data, and the requirement of a FoxAPIs key. These are exactly the operational constraints an agent needs before spending budget. It stops short of describing pagination or rate limits, so 4 not 5.

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 compact sentences: the first front-loads what is returned and the input, the second front-loads cost and auth. No filler, no repetition of the title, and every clause carries distinct information.

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 no output schema, the description compensates by enumerating the returned fields, and it covers the two things an agent would otherwise get wrong: the identifier type and the credit/auth preconditions. For a one-parameter read tool with rich annotations, nothing material 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 coverage is 100% for the single `channel` parameter, including an example value, so the schema already carries the semantics. The description reinforces that the input is a channel name rather than an ID or URL, which is a useful disambiguation but adds little beyond the schema. 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?

Names a specific resource (a Twitch channel) and enumerates the payload it yields: followers, partner status, live status, latest video, keyed by channel name. An agent can immediately tell this apart from youtube_channel or bluesky_post because the resource and data fields are explicit. It does not explicitly name a sibling it is not, so 4 rather than 5.

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?

The phrase "from the channel name" implies the lookup is by identifier, and the credit note implicitly signals this is a paid call to use deliberately. However, there is no explicit when-to-use or when-not guidance, and no routing statement toward or away from the sibling channel tools. Usage is inferable but not 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