Set the AI's response depth mode to control how detailed Bible answers are. Choose from auto, minimal, short, medium, detailed, deep, or verses_only to match your need.
Set active AI response depth mode.
| Name | Required | Description | Default |
|---|---|---|---|
| mode | Yes | Mode ('auto', 'minimal', 'short', 'medium', 'detailed', 'deep', 'verses_only') |
Changes observed during successful MCP inspections.
v2.0.0Does 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, but it only states that a mode is set. It does not explain whether the setting persists, whether it affects only subsequent responses, or whether it resets to a default, leaving the actual side effects and scope ambiguous.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single, front-loaded sentence with no filler words. It is appropriately sized for a simple one-parameter configuration tool, and every word contributes meaning.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a one-parameter tool with full schema coverage, the description plus schema is minimally sufficient for an agent to call it, but the lack of annotations and output schema leaves the behavior and effect scope under-specified. A brief sentence about what 'active' mode applies to would complete the context.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, and the mode parameter's allowed values are already fully enumerated in the schema. The description adds 'active' and 'response depth' context but no additional syntactic or semantic detail beyond what the schema provides, so the baseline of 3 is appropriate.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description 'Set active AI response depth mode' clearly identifies a specific verb and resource: it changes the AI response depth mode. It is distinguishable from the many search/retrieval siblings, though it does not explicitly differentiate from other setter tools like set_relevance_sensitivity or set_show_metrics.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
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, when not to use it, or how it relates to sibling configuration tools. The mode values in the schema imply intent, but there is no explicit usage context or alternative mention.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.