Skip to main content
Glama
Fetchproof MCP Server

Fetchproof MCP Server

twitch_profile

Retrieve a Twitch profile by handle to get channel details for verification, research, or display. Supply the handle to fetch public profile data from Twitch.

Instructions

twitch: Profile. GET /v1/twitch/profile. Get Twitch profile 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_profile"
  }
}

Input Schema

NameRequiredDescriptionDefault
handleYesTwitch handle
cache_max_ageNoUse a cached response this old or newer for 0 credits. If none is available, fetch live at the endpoint’s normal price.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior4/5

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

With no annotations, the description carries the full behavioral burden and does well on cost semantics: 1 credit on success, free on errors/blocked/timeouts/invalid requests/cache hits. It also implicitly identifies this as a read operation via the GET route. It stops short of describing auth requirements, rate limits, or what the returned profile contains.

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 purpose and endpoint are front-loaded and efficient, but the trailing cost paragraph is generic boilerplate, and the sentence "A not-found or empty result is charged only where that operation's published cost says so" adds little that the preceding sentence didn't already cover.

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?

For a simple two-parameter read tool the scope and pricing are adequately covered, but there is no output schema and the description never says what fields a profile returns or how a not-found case is signalled. An agent knows how to call it but not quite what to expect back.

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%, including the examples for handle and the full semantics of cache_max_age, so the schema already does this work. The description only corroborates the caching cost behavior ("cache hits cost nothing") without adding syntax or constraints 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?

"Get Twitch profile" plus the underlying route GET /v1/twitch/profile states a specific verb and resource, so an agent knows exactly what it does. It does not explicitly distinguish itself from platform-sibling tools such as twitch_user_videos or twitch_clip, but the scope (a single profile by handle) is unambiguous.

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 by the purpose statement; there is no explicit when-to-use, when-not-to-use, or alternative routing guidance. Nothing tells the agent how this differs from other Twitch tools that also take a handle, so selection must be inferred from the name alone.

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