Skip to main content
Glama

Twitch

by io.github.pipeworx-io

Remember

remember
Idempotent

Save data the agent will need to reuse later — across this conversation or across sessions. Use when you discover something worth carrying forward (a resolved ticker, a target address, a user preference, a research subject) so you don't have to look it up again. Stored as a key-value pair scoped by your identifier. Authenticated users get persistent memory; anonymous sessions retain memory for 24 hours. Pair with recall to retrieve later, forget to delete.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
keyYesMemory key (e.g., "subject_property", "target_ticker", "user_preference")
valueYesValue to store (any text — findings, addresses, preferences, notes)

TDQS

A4.5/5.0
Behavior5/5

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

The description adds behavioral context beyond annotations: key-value scoping by identifier, persistence for authenticated users, and 24-hour retention for anonymous sessions. This complements the idempotentHint and destructiveHint annotations without contradiction, providing a complete behavioral profile.

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 description is three sentences with no wasted words. It is front-loaded with the core purpose, followed by usage guidelines and behavioral details. Every sentence earns its place.

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?

Given the tool's simplicity (two required string params, no output schema), the description covers purpose, usage, storage behavior, lifetime, and sibling tools. It is complete for an agent to select and invoke correctly, even without additional structured information.

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%, so the baseline is 3. The description's examples (e.g., 'subject_property') add minor context but do not significantly enhance understanding beyond the schema descriptions. The value is adequate but not exceptional.

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 uses a specific verb ('Save') and resource ('data') and clearly states the purpose ('reuse later across conversations or sessions'). It distinguishes from sibling tools by mentioning 'recall' and 'forget', making it clear what this tool does versus others.

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 description explicitly says 'Use when you discover something worth carrying forward' and provides examples (ticker, address, preference). It also recommends pairing with recall and forget. While it doesn't explicitly state when not to use, the guidance is clear and sufficient for an AI agent.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Twitch toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.7/5.0
Disambiguation2/5

The tool set includes many similar Pipeworx query tools (ask_pipeworx, ask_pipeworx_grounded, ask_pipeworx_beta, deep_research) that all serve overlapping purposes, causing confusion. The Twitch-specific tools are distinct but are buried among many unrelated tools.

Naming Consistency3/5

Most tools use snake_case (e.g., get_streams, ask_pipeworx), but there is variation in patterns: some are verb_ noun (get_streams), some are just verbs (remember), and some are adjective_noun (recent_changes). No strong pattern across the whole set.

Tool Count2/5

With 35 tools, the server is bloated for its stated purpose as a 'Twitch' server. Only about 4-5 tools are Twitch-related; the rest are from a data platform (Pipeworx) and generic utilities, making the count feel excessive and unfocused.

Completeness2/5

For a Twitch server, the tool surface is severely incomplete. It lacks essential Twitch features like clips, follows, chat, or channel management. The few Twitch tools present cover only basic stream and user lookup.

Resources