Hook Detector

create_key

Create another API key on your account, for example one per agent or machine, so you can revoke one without touching the others. name is up to 60 characters.

Give the key only what it needs. scopes: any of "read" (read runs, hooks, keeps,
usage), "write" (keep, reject, undo, chat), "research" (start runs, which spend
credits), "admin" (manage keys, delete the account); all four when left out. An agent
that finds hooks needs ["read", "write", "research"]. credit_limit: the most credits
runs started with this key may spend over its life, 1 to 100000 (a run then reserves
at most what is left). expires_in_days: 1 to 365; the key then stops working (401
key_expired).

The new key is in this result once and never again: store it now. Needs admin. An
account holds at most 10 active keys (409 beyond) and may create 20 per hour by
default (429 beyond). Free.
Next step: use the returned api_key; revoke old ones with revoke_key.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`name`	No
`scopes`	No
`api_key`	No
`credit_limit`	No
`expires_in_days`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedSep 25, 2026

TDQS

A4.7/5.0

Behavior5/5

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

With no annotations present, the description fully carries the behavioral burden and does so thoroughly: the key appears only once, admin is required, quotas are disclosed (10 active keys, 20/hour), expiry produces 401 key_expired, credit reservations are explained, and scope side effects like spending credits are spelled out.

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?

The description is long but every sentence earns its place. Purpose is front-loaded, parameters are grouped into focused clauses, and quotas, auth, and next steps form compact, readable sections. There is no tautology or filler.

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?

This is a complex credential-creation tool with no annotations and no schema descriptions, yet the description covers purpose, defaults, side effects, quotas, errors, auth requirements, and next steps. The output schema covers the return shape, and the description adds the critical storage warning. The only minor gap is the undocumented api_key input parameter.

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

Parameters4/5

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

The description compensates for 0% schema coverage by explaining name length, all scope values with their meanings and defaults, credit_limit range and behavior, and expires_in_days bounds. However, the api_key input parameter is never explained; an agent is left to guess what it means or whether to provide it.

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 first sentence states a specific verb and resource: 'Create another API key on your account', and gives a concrete motivating use case (one per agent or machine) so an agent can distinguish it from sibling tools like revoke_key or list_keys. The purpose is unmistakable.

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?

The description gives clear context: create separate keys for separate agents/machines, apply least-privilege scopes, and 'Needs admin' sets an important prerequisite. It also points to revoke_key as the next step, but it does not explicitly say when not to use this tool versus alternatives like list_keys or revoke_key.

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?