Skip to main content
Glama

Metis · Librarian — Set Knowledge Layer Enabled

set_knowledge_layer_enabled

Enable or disable a knowledge background layer for searches so off-topic documents stop influencing answers when searching all layers; disabling does not delete the layer.

Instructions

Turn a knowledge background layer on or off for searching.

A disabled layer is skipped when a question searches "all" layers, so its
documents stop influencing answers — useful when a background is off-topic for
the work at hand. It is not deleted, and naming it explicitly in a search still
reaches it.

Args:
    database: The layer's slug (e.g. 'ph-background', 'epi-methods').
    enabled: True to include it in searches, False to exclude it.

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": {
      "database": "<database>"
    },
    "name": "set_knowledge_layer_enabled"
  }
}

Input Schema

NameRequiredDescriptionDefault
enabledNo
databaseYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.5

TDQS

A4/5.0
Behavior4/5

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

With no annotations provided, the description carries the full burden and does well: it discloses persistence ('it is not deleted'), the exact search consequence (skipped in 'all' searches, documents stop influencing answers), the bypass path (explicit naming still reaches it), and thereby reversibility. It omits error behavior and any permission or scope requirements.

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?

The behavior clause is front-loaded ahead of the rationale, and the args block is terse. The trade-off explanation ('stop influencing answers') is warranted; the args section retreads parameter names already visible in the schema, which costs a little space.

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?

A two-parameter reversible toggle with an output schema, so return values need no exposition, and the description covers persistence and search semantics thoroughly. Only minor items are absent: the default value of 'enabled' and what happens on an unknown slug or a permission failure.

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?

Schema description coverage is 0%, so the description must compensate, and it largely does: 'database' is explained as the layer's slug with two concrete examples, and 'enabled' is glossed as True to include / False to exclude. The one gap is that the schema default of true for 'enabled' is never mentioned.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

A specific verb-plus-resource: 'Turn a knowledge background layer on or off for searching' states the object and the effect precisely. It also implicitly differentiates itself from delete_knowledge_database by clarifying the layer 'is not deleted', though it never names a sibling tool explicitly.

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?

'Useful when a background is off-topic for the work at hand' gives a concrete when-to-use condition, and the note that explicit naming in a search still reaches a disabled layer tells the agent the toggle is non-destructive. It stops short of naming alternatives such as delete_knowledge_database or list_knowledge_databases.

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