Hook Detector

get_shared_folder

A shared folder as anyone with its link sees it: name, description, kind, item_count and items (public fields and the owner's note), newest first, paged. No key needed; limited per address (429). A link never made or turned off is 404 shared_folder_not_found. Same as GET /v1/shared/folders/{token}. Free.

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

Input Schema

Name	Required	Description
`limit`	No	page size, 1 to 100
`token`	No	the token of a share link (hookdetector.com/f/<token>)
`cursor`	No

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 26, 2026

TDQS

A4/5.0

Behavior5/5

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

With no annotations, the description carries the full burden and does so well: it discloses ordering ('newest first'), pagination, per-address rate limiting with 429, and the exact 404 error name for a link that was never made or was turned off. These are the operational facts an agent needs before committing to a call.

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?

Front-loaded with what the resource is, followed by return shape, ordering, auth, rate limits and error semantics in a compact telegraphic style. Every clause adds a fact; nothing is boilerplate.

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

Completeness4/5

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

For an anonymous read tool with an output schema, auth requirements, cost, pagination, rate limiting and the failure mode are all covered. Minor gaps: it doesn't indicate that pagination is driven by the undocumented cursor, and it doesn't say where a token comes from (share_folder).

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 67%; token and limit are documented in the schema, while cursor has no description there. The description only adds the notion of paging ('paged'), which loosely explains cursor, and restates nothing else about limit bounds. Useful but minimal compensation for the undocumented cursor parameter.

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 ('a shared folder') and its access mode ('as anyone with its link sees it'), then enumerates the returned fields and ordering. It also maps to the REST endpoint GET /v1/shared/folders/{token}. It does not explicitly contrast with the sibling get_folder (owner view), so sibling differentiation is implied rather than stated.

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?

'No key needed' and 'Free' tell the agent this is the anonymous path, and the 404 code tells it what a missing/disabled link looks like. However, it never says when to prefer this over get_folder or share_folder, so the choice between the owner view and the public view is left to inference.

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?