Seltz web research
Use the configured Seltz MCP server when the user needs current web information, recent developments,
source discovery, or a fact check. The documented v1 surface exposes one tool:
search: required query string; optional max_results integer, default 10.
Operating rules
- Turn the user's request into a concise, specific query. Include a date, jurisdiction, product, or
domain when it materially narrows the research question.
- Keep
max_results small enough for the task. Ask for more only when the first results leave a clear
evidence gap.
- Preserve source URLs and publication dates from the tool result. Distinguish Seltz output from your
own synthesis, and tell the user when a claim is time-sensitive or only supported by one source.
- Prefer primary, official, or directly attributable sources for legal, financial, medical, security,
and product claims. Do not treat ranking as proof.
- Do not send API keys, passwords, payment credentials, private account data, or unnecessary personal
information in a query.
- Do not imply that Seltz fetched a page, verified a fact, or returned an exhaustive result set unless
the live tool response explicitly supports that statement.
Failure handling
- Authentication or permission failures: ask the user to reconnect Seltz in Codex and re-enter the API
key; never ask them to paste the key into the conversation.
- Rate or usage limits: report the limit, honor any retry timing returned by the server, and do not loop.
- Timeouts or unavailable service: retry at most once when the request is safe and idempotent, then offer
a fallback that does not pretend to have current Seltz data.
- Malformed or incomplete results: say what is missing, preserve any usable source links, and do not
manufacture fields or citations.
Safe response pattern
For research answers, state the question and retrieval time, summarize the strongest sources, link them,
and call out uncertainty, conflicting evidence, or missing coverage. For fact checks, separate the verdict
from the evidence and explain what would change the conclusion.
1---2name: seltz3description: Use Seltz's official MCP search tool for current, source-backed web research in Codex.4license: Apache-2.05---67# Seltz web research89Use the configured Seltz MCP server when the user needs current web information, recent developments,10source discovery, or a fact check. The documented v1 surface exposes one tool:1112- `search`: required `query` string; optional `max_results` integer, default `10`.1314## Operating rules15161. Turn the user's request into a concise, specific query. Include a date, jurisdiction, product, or17 domain when it materially narrows the research question.182. Keep `max_results` small enough for the task. Ask for more only when the first results leave a clear19 evidence gap.203. Preserve source URLs and publication dates from the tool result. Distinguish Seltz output from your21 own synthesis, and tell the user when a claim is time-sensitive or only supported by one source.224. Prefer primary, official, or directly attributable sources for legal, financial, medical, security,23 and product claims. Do not treat ranking as proof.245. Do not send API keys, passwords, payment credentials, private account data, or unnecessary personal25 information in a query.266. Do not imply that Seltz fetched a page, verified a fact, or returned an exhaustive result set unless27 the live tool response explicitly supports that statement.2829## Failure handling3031- Authentication or permission failures: ask the user to reconnect Seltz in Codex and re-enter the API32 key; never ask them to paste the key into the conversation.33- Rate or usage limits: report the limit, honor any retry timing returned by the server, and do not loop.34- Timeouts or unavailable service: retry at most once when the request is safe and idempotent, then offer35 a fallback that does not pretend to have current Seltz data.36- Malformed or incomplete results: say what is missing, preserve any usable source links, and do not37 manufacture fields or citations.3839## Safe response pattern4041For research answers, state the question and retrieval time, summarize the strongest sources, link them,42and call out uncertainty, conflicting evidence, or missing coverage. For fact checks, separate the verdict43from the evidence and explain what would change the conclusion.
hashgraph-online