# Relewise Search Tools

> Inspect and update Relewise Search Tools configuration. Use for Search Indexes and decompounding, redirect, result-modifier, search-term-modifier, stemming, or synonym rules.

- Skill: `relewise/relewise-search-tools` (Agent Skill, multi-file: 3 files)
- Install (CLI): `npx skillmds@latest add relewise/relewise-search-tools`
- Raw SKILL.md: https://api.skillmd.com/api/skills/relewise/relewise-search-tools/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: Relewise (https://skillmd.com/u/relewise)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/relewise/relewise-search-tools

---


# Relewise Search Tools

Before any Agent Gateway call, activate and follow the installed `relewise-agent-gateway` skill from this plugin. Pass it the selected REST operation ID and/or MCP tool plus validated parameters; do not resolve the CLI, choose a transport, or handle authentication in this domain skill. Discover and validate the intended Dataset first. Dataset-specific Data Keys and values are case-sensitive; retrieve metadata when they are unknown rather than guessing. Inspect the selected transport's schema before using an unfamiliar operation or related MCP tool.

Read [references/rule-workflows.md](references/rule-workflows.md) to select the correct rule family and operation sequence.

## Inspect configuration

When an ID is unknown, use the relevant list operation and then the matching get operation for complete configuration. Search Index operations are currently read-only.

## Modify configuration

Patch operations change live search behavior. Use them only for an explicit user request; audits and recommendations authorize reads, not writes.

Before patching:

1. Resolve the exact Dataset, rule family, and rule ID.
2. Retrieve the rule's complete current configuration.
3. Inspect the selected transport's current mutation schema. MCP approval tools accept narrower inputs than their related REST patch operations.
4. Send only intended changes. An omitted or `null` property preserves its current value unless the schema explicitly states otherwise.

Do not translate a request into a different rule family merely because it has a similar name. After mutation, identify the Dataset, rule, and fields changed, and surface any API warning or validation error without identical retries.