Hook Detector

channel_outliers

A channel's own outliers (scope own), or outliers for a channel like it from other channels in the shared index (scope niche, 3x and over by default). Free. Same as GET /v1/channels/{ref}/outliers.

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": {
      "ref": "<ref>"
    },
    "name": "channel_outliers"
  }
}

Input Schema

Name	Required	Description	Default
`ref`	Yes
`limit`	No
`scope`	No	own or niche	own
`api_key`	No
`min_multiple`	No

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 26, 2026

TDQS

B3.2/5.0

Behavior2/5

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

With no annotations, the description carries the full behavioral burden. It usefully discloses that the call is 'Free' and that niche scope defaults to a 3x threshold, but it omits auth requirements, rate limits, pagination/limit behavior, ordering, and what counts as an outlier. The endpoint reference is not a substitute for behavioral context.

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?

The description is short and front-loads the scope distinction before the pricing and endpoint notes. It is efficient, though the parenthetical compression makes it slightly cryptic rather than maximally readable.

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?

An output schema exists, so return-value details need not be explained. Still, for a five-parameter read tool with no annotations, the description is minimal: it covers scope and free access but not auth, limit semantics, ref format, or pagination. It is adequate to start but not complete.

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 only 20%, so the description must compensate more. It does clarify `scope` values and the default min threshold for niche mode, which adds real meaning beyond the schema. But `limit`, `api_key`, and `ref` semantics remain undocumented in both places, leaving substantial gaps.

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?

The description identifies a specific resource (a channel's outliers) and distinguishes two modes: own-channel vs. niche/shared-index outliers. It also maps directly to an endpoint, which makes the operation concrete. It stops short of a clean verb+object statement because the phrasing is dense and assumes familiarity with 'outliers' and 'niche'.

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?

It explains the meaning of the two `scope` values, including the default '3x and over' threshold for niche, which implies when each mode applies. However, it does not explicitly route the agent against siblings like `random_outliers`, `niche_report`, or `similar_channels`, and does not state prerequisites or exclusions.

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

All Hook Detector tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?