Hook Detector

revoke_key

Revoke one of your API keys at once: key_id from list_keys, or "original" for the signup key. Any key may revoke itself (the result says so, and that key stops working immediately); revoking another needs admin. Never the last active key on the account (409): create another with create_key first.

If a key leaked, pass key_id "others": every key of the account except the one you
are calling with is revoked at once, and the result says how many (revoked_count) and
which key is kept. Needs admin. Free.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`key_id`	Yes
`api_key`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedSep 25, 2026

TDQS

A5/5.0

Behavior5/5

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

With no annotations provided, the description carries the full burden. It discloses all critical behaviors: self-revocation works immediately, revoking others requires admin, the last active key cannot be revoked, and the 'others' special value revokes all but the calling key. It also states the result fields (revoked_count and retained key) and cost implications ('Free'). This is exceptionally transparent.

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 dense but every sentence contributes essential information. The main use case is front-loaded, then constraints and edge cases follow logically. The special 'others' case is given its own paragraph, improving readability. No filler or redundancy.

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?

Given the tool's complexity (special values, admin requirements, error conditions, output details), the description covers all aspects: the key_id special cases, permission model, 409 failure mode, result format, and cost. It even explains the behavior of the 'others' case in detail. An agent armed with this description can invoke the tool correctly in every scenario.

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

Parameters5/5

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

Schema coverage is 0%, so the description must explain parameters. Key_id is thoroughly explained, including special values 'original' and 'others', and the behavior they trigger. The api_key parameter is implicitly covered by the phrase 'the one you are calling with', clarifying its role in the revocation. The description adds meaning far beyond the raw schema fields.

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 description begins with 'Revoke one of your API keys at once' – a specific verb, resource, and scope. It also distinguishes itself from siblings by mentioning 'list_keys' and 'create_key' directly, making it clear which tool to use for key management actions.

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

Usage Guidelines5/5

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

It explicitly states when to use the tool (to revoke keys), when to use alternatives (create another key before revoking the last), and when to use the special 'others' value for leaked keys. It also outlines conditional requirements like admin privileges and the 409 restriction, leaving no ambiguity about invocation conditions.

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?