Hook Detector

format_videos

One title format's videos, strongest first. Free. Same as GET /v1/formats/{format_id}.

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": {
      "format_id": "<format_id>"
    },
    "name": "format_videos"
  }
}

Input Schema

Name	Required	Description	Default
`limit`	No
`api_key`	No
`format_id`	Yes

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 26, 2026

TDQS

B3/5.0

Behavior3/5

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

With no annotations, the description must carry the disclosure burden; it does add two useful facts: the call costs no credits and results are ordered strongest-first. It says nothing about pagination, quota/rate behavior, or auth handling (api_key param), which is a meaningful gap for a no-annotation tool.

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 short fragments, front-loaded with the resource and ordering, no wasted prose. The REST-equivalence sentence earns its place only as the sole hint about the required path parameter, though it is niche knowledge.

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 fields needn't be explained, and the ID/ordering/cost essentials are present. Missing pagination semantics for limit and any auth/cost context for api_key keep it at minimum viable.

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%, so the description must compensate, yet it only indirectly identifies format_id via the REST path template. The limit and api_key parameters are never mentioned, leaving a third of the surface undocumented.

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?

States a specific resource — the videos belonging to one title format — plus the output ordering ('strongest first'), which distinguishes it from list_formats and generic listers. The verb is implicit rather than stated ('list'), which keeps it just short of a 5.

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?

'Free' hints at credit cost, but there is no when-to-use guidance, no mention of list_formats as the sibling for enumerating formats, and no exclusions. The REST pointer ('Same as GET /v1/formats/{format_id}') assumes the agent knows the external API rather than explaining the tool itself.

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?