HookSend

Update a knowledge base

knowledge_update

Changes a knowledge base's name, its description, the keywords that hand a DM to it, whether it answers only when one of those keywords matches, its fallback message, or whether it is switched on. Only the fields you pass are changed, and every one of them can be set back. Switching one on is the only part a plan can refuse: a plan allows so many live at once, and the refusal says how many and what to do about it. Switching one off is always allowed and loses none of its documents, so use that rather than asking for a knowledge base to be deleted.

Input Schema

Name	Required	Description
`name`	No	A new name for it.
`isActive`	No	True to switch the knowledge base on so it answers DMs, false to switch it off.
`keywords`	No	The words in a DM that should be answered from this knowledge base, up to twenty.
`description`	No	A new description, or null to clear it.
`keywordsOnly`	No	True to make this knowledge base answer only DMs that contain one of its keywords, and the conversation that follows. "Answer every DM" then never uses it, so its documents never reach anyone who did not type a keyword: right for material meant for a few people, such as a partner or wholesale FAQ. A campaign that names this knowledge base still answers from it. It needs at least one keyword, or it never answers. False to let "Answer every DM" use it again.
`wholeWordMatch`	No	True to match those keywords only as whole words.
`fallbackMessage`	No	What to reply when the documents do not answer the question, or null for none.
`knowledgeBaseId`	Yes	The id of the knowledge base.

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 5, 2026

TDQS

A4.4/5.0

Behavior5/5

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

Annotations only say non-read-only and non-destructive. The description layers on genuinely new context: PATCH semantics ("Only the fields you pass are changed"), reversibility ("every one of them can be set back"), a plan-limited failure mode for activation plus what the refusal reports, and the guarantee that switching off loses no documents.

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 purpose, then partial-update semantics, then the activation caveat and the disable-vs-delete advice — a logical order where each sentence carries weight. It is dense and the field enumeration partially duplicates the schema's own descriptions, costing a little efficiency.

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?

For an 8-parameter settings update with full schema coverage and no output schema, the description supplies the operational facts an agent needs: partial semantics, reversibility, the plan limit that can reject activation, and the safe deactivation alternative. Nothing required to call it correctly is missing.

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?

Schema description coverage is 100%, so every parameter is already documented at the field level and the baseline is 3. The description restates the same field list without adding syntax, formats, or per-parameter constraints beyond what the schema provides.

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?

Opens with a specific verb+resource ("Changes a knowledge base's") and then enumerates the mutable surface — name, description, keywords, keyword-only mode, fallback message, and active state. An agent can tell this is the settings-mutation tool distinct from knowledge_create or knowledge_add_document without opening the schema.

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 one explicit routing directive — "use that rather than asking for a knowledge base to be deleted" — which steers the agent away from a destructive path. However, it never frames when to reach for this tool versus siblings like knowledge_ai_settings_update, so guidance is solid but not exhaustive.

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

All HookSend 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?