Skip to main content
Glama
yucx-go

agent-knowledge

by yucx-go

ak_hook_fire

Fire a single UMSF event for real-time knowledge capture, wrapping it in a one-event document and dispatching through the hook system. For multi-event submissions, use ak_ingest_umsf.

Instructions

Fire a single UMSF event for real-time knowledge capture. The event is wrapped in a one-event UMSFDocument and dispatched through the hook system. For multi-event submissions, use ak_ingest_umsf.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
argsNoFor 'tool_use' events: structured tool arguments.
nameNoFor 'tool_use' events: tool name. For 'error' events: failing tool.
pathNoFor 'file_change' events: filesystem path.
roleNoFor 'message' events: user / assistant / system / tool.
typeYesUMSF event type: message, tool_use, tool_result, decision, file_change, error, session_start, session_end.
agentNoAgent identifier (claude-code / codex / hermes / external).external
errorNoFor 'error' events: error message.
resultNoFor 'tool_result' events: stringified tool output.
contentNoMessage body / decision text / error description.
metadataNoFree-form metadata (e.g. session_end events may pass {messages: [...]}).
session_idNoSession identifier (optional).
Behavior3/5

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

No annotations are provided, so the description carries the behavioral disclosure burden. It reveals that the event is wrapped in a one-event UMSFDocument and dispatched through the hook system, offering useful internal context. However, it does not mention return values, error handling, or asynchronous execution, which would be valuable for a mutation tool.

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 two sentences: the first states the action and purpose, the second provides an alternative. It is front-loaded, efficient, and contains no redundant 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 11-parameter schema with complete coverage and the clear alternative to a sibling tool, the description is largely complete. It lacks an example or notes on response behavior, but the essential context for selection and invocation is present.

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?

The schema covers all 11 parameters with descriptions, so the baseline is 3. The description adds no parameter-level detail beyond the schema, but its focus on 'single event' aligns with the schema's type field and does not conflict.

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 clearly states the action ('Fire a single UMSF event') with a specific verb and resource, and explicitly distinguishes from the sibling tool ak_ingest_umsf by emphasizing single vs multi-event submissions.

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?

The description provides explicit guidance: use this for a single event and use ak_ingest_umsf for multi-event submissions, naming the alternative tool and the condition under which it should be used.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/yucx-go/agent-knowledge'

If you have feedback or need assistance with the MCP directory API, please join our Discord server