Skip to main content
Glama
Sign In
agent-knowledge

agent-knowledge

by yucx-go
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

ak_hook_list

List all registered hooks to view active event handlers and integrations. Useful for auditing hook configurations and verifying current registrations.

Instructions

List all registered hooks.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.1

TDQS

A3.8/5.0
Behavior3/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It accurately indicates a non-destructive 'list' operation and clarifies scope ('all' hooks), but it does not mention potential side effects, permissions, or whether hooks are returned in a particular order. For a simple read-only operation, this is adequate but minimal.

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 a single, front-loaded sentence that wastes no words. It states the action and resource clearly without any superfluous information.

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?

Given the low complexity (no parameters, no output schema), the description is sufficiently complete. It conveys the core purpose and implies the return value (a list of hooks). However, it does not specify the format of the returned data or any relevant details about hook attributes, which would require an output schema or additional explanation.

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 tool has zero parameters and the schema is empty, making description of parameters unnecessary. The baseline for 0 params is 4, and the description does not need to compensate for any missing schema information because there is nothing to document.

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 'List all registered hooks' uses a specific verb (list) and a specific resource (registered hooks), making the purpose immediately clear. It also distinguishes itself from siblings like ak_hook_fire and ak_hook_stats by implying enumeration rather than execution or statistics.

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?

The description provides no guidance on when to use this tool versus alternatives. It does not mention that this is the appropriate tool for simply viewing hooks, nor does it exclude cases where ak_hook_stats might be more useful. The only context is the name and sibling names, which are not explicitly referenced in the description.

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

Deploy Server

Other Tools