Skip to main content
Glama

Find a streamer tool

search_tools
Read-onlyIdempotent

Search the TwitchBoard catalog of free browser tools for streamers (Twitch, OBS, YouTube, Discord, TikTok, Kick, stream graphics, name generators). Use it when the user needs to do something hands-on that needs a UI, such as resizing an emote, designing a panel, making a banner or setting up an overlay, and you want to send them to a free tool that does it. Returns matching tools with a one-line description and URL. Leave "query" empty to list a whole category.

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

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum number of tools to return.
queryNoWhat the user wants to do, e.g. "resize emote", "starting soon screen", "chat overlay".
categoryNoOptional: only search one category.

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?

Annotations already establish read-only, idempotent, closed-world, non-destructive behavior, so the description isn't burdened with a safety story. It usefully adds what the annotations cannot: the return shape (matching tools with a one-line description and URL) and the special empty-query behavior for category browsing.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three sentences, front-loaded with the purpose and then the trigger condition; nothing is padding. The parenthetical platform list slightly duplicates the category enum already in the schema, which is the only redundancy.

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 correctly compensates by stating what comes back (name-level description plus URL). All three optional parameters are covered and the tool's complexity is low, so an agent has everything needed to decide to call it and how.

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%, so all three parameters are already documented, and the baseline is 3. The description adds one genuinely new semantic — leaving "query" empty lists an entire category rather than returning nothing — which is a small but real contribution over the schema.

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 verb and resource ("Search the TwitchBoard catalog of free browser tools for streamers") and scopes it with concrete domains (Twitch, OBS, YouTube, Discord, TikTok, Kick, graphics, names). That scope cleanly separates it from siblings like generate_names or create_obs_widget, which perform work in-tool rather than pointing at an external UI tool.

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?

It gives an explicit use condition — the user needs something hands-on that requires a UI — plus four concrete example tasks (resize emote, design panel, banner, overlay). What's missing is an explicit exclusion naming a sibling to prefer when the task does not need a UI, but the "needs a UI" framing does most of that routing work implicitly.

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