Hook Detector

random_outliers

Outliers at random from the shared index (5x their channel's usual and over by default), a different set each call. Free. Same as GET /v1/index/random.

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

Input Schema

Name	Required	Description	Default
`limit`	No
`api_key`	No
`language`	No
`max_views`	No
`min_views`	No
`channel_size`	No
`content_type`	No
`max_multiple`	No
`min_multiple`	No
`posted_within_days`	No

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 26, 2026

TDQS

C2.9/5.0

Behavior3/5

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

With no annotations, the description does useful work: it discloses that results are non-deterministic ('a different set each call'), that the call consumes no credits ('Free'), and the default outlier threshold. It does not cover authentication (the api_key param), rate limits, or pagination/return shape beyond what the output schema already provides.

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?

Very compact and front-loaded: the core selection behavior and the non-determinism arrive in the first sentence, with cost and the HTTP endpoint mapping in a short tail. Slight ambiguity from the compressed phrasing but no wasted sentences.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a tool with 10 optional parameters, zero schema documentation, and no annotations, the description leaves an agent unable to use any filter meaningfully. The output schema covers return values, but the input contract is essentially undocumented.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% across 10 parameters, and the description explains almost none of them — only the implicit default for min_multiple ('5x their channel's usual and over'). Terms like channel_size, content_type, min/max_multiple, posted_within_days, and language are left entirely unexplained, which is a large gap for a 10-param tool.

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 names the resource (shared index) and the selection logic (random outliers, a different set each call), plus a concrete threshold definition for 'outlier' (5x their channel's usual views). It implicitly distinguishes itself from search_index by offering randomized discovery rather than querying, though it never names that sibling.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use guidance, no exclusions, and no reference to search_index or any other sibling as the alternative for directed lookup. 'Free' hints at cost behavior but not at when this tool is the right choice.

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?