Adjust the pastoral and ethical warmth of Bible search results by setting a sensitivity score from 0 to 100. Higher scores increase empathetic and ethically considerate responses.
Set pastoral/ethical warmth sensitivity score (0 to 100).
| Name | Required | Description | Default |
|---|---|---|---|
| score | Yes | Sensitivity score (0 to 100) |
Changes observed during successful MCP inspections.
v2.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden of behavioral disclosure. While it clearly indicates a mutation ('Set'), it does not explain what the score actually affects, whether the setting persists, or what higher versus lower values mean for behavior.
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 sentence, front-loaded with the action verb, and contains no wasted words. It is appropriately minimal for a one-parameter setter.
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?
The tool is simple and the schema covers the parameter, so the description is not grossly incomplete. However, it lacks value semantics (what does 0 versus 100 mean?) and does not clarify the practical effect of setting the score, which an agent would need to use it confidently.
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 coverage is 100%, so the schema already documents the single parameter and its range. The description essentially repeats the 0-to-100 range without adding meaning about how the score is interpreted.
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 states a specific verb ('Set') and a specific resource ('pastoral/ethical warmth sensitivity score') with a clear numeric range. It is distinguishable from sibling setters like set_response_mode and set_show_metrics by naming the setting it changes.
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?
There is no guidance about when to use this tool versus other configuration tools, nor is there any context about how it interacts with response mode or metrics settings. The intended use must be inferred from the tool name and sibling context.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.