AnyHook

Inspect a specific event

anyhook_inspect

Read-onlyIdempotent

Full detail for one event by id, including the inbound headers and body that anyhook_events omits, plus the destination's response. Payloads can be large and often contain personal data, so it reads one event at a time, for when the body is needed. Account or local store.

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": {
      "id": "<id>"
    },
    "name": "anyhook_inspect"
  }
}

Input Schema

Name	Required	Description	Default
`id`	Yes	Event ID returned by anyhook_events.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 27, 2026
- removedInput schema / additionalProperties
```
Removed value: -false
```

Changed1 schema field changedOct 22, 2026

removedInput schema / properties / api_key

Removed value: -{
-  "description": "API key (ahk_live_...) from anyhook_quickstart. Only needed over HTTP when no Authorization header is set; ignored over stdio.",
-  "type": "string"
-}

First observedJul 29, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, and the description adds real context beyond them: payloads can be large, often contain personal data, and the read is deliberately scoped to a single event. It does not explain pagination or size limits, but the privacy and volume warnings are genuinely useful additions.

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?

Front-loads the return contents and the sibling contrast in a compact two-sentence block. The dangling 'Account or local store.' phrase is cryptic and slightly undercuts the otherwise tight structure.

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?

No output schema exists, so the description appropriately enumerates the return payload (headers, body, destination response) and warns about size and personal data. Enough for an agent to call it correctly; only the ambiguous source phrase and absent size/limit guidance leave minor gaps.

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?

With one parameter and 100% schema coverage, the schema already documents that id is an event ID from anyhook_events. The description's 'by id' adds no syntax or format detail beyond that, so it sits at the baseline where the schema does the work.

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?

States a specific verb ('inspect'), resource ('one event by id'), and the exact contents returned (inbound headers, body, destination response). It explicitly contrasts with anyhook_events by noting that tool omits headers/body, so an agent can distinguish the two without reading schemas.

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?

Gives a clear selection condition: use this 'for when the body is needed', versus the lighter anyhook_events listing. It also notes the one-at-a-time read pattern, which shapes usage. The trailing fragment 'Account or local store.' is ambiguous and doesn't clarify when each source applies.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All AnyHook tools Inspect

Try in Browser

Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.