Browse documentation
why_not
Coverage transparency: is this URL in the index, and if not, what happened to it?
Behaviour
Answers one of three things. `present` returns the hit. `removed` names the reason — redundant, superseded, stale, access-starved, lost-replacement, or tombstoned-source — and, where one exists, the passage that superseded it. `unknown` means it was never admitted, or was never seen.
Use it before concluding the web is silent on something: an absent URL and an absent topic are different findings.
Arguments
inputSchema
| Name | Type | Description |
|---|---|---|
urlrequired | string | The URL to ask about |
Returns
A JSON payload in the text content block, and the same payload as
structuredContent for clients that support it.
outputSchema
| Name | Type | Description |
|---|---|---|
hit | object | — |
reason | "redundant" | "superseded" | "stale" | "access-starved" | "lost-replacement" | "tombstoned-source" | — |
removed_at | integer | — |
statusrequired | "present" | "removed" | "unknown" | — |
superseded_by | string | null | The passage id that replaced it, when there is one |
Calling it
Over Streamable HTTP, with the required arguments filled in:
{
"jsonrpc": "2.0",
"id": 1,
"method": "tools/call",
"params": {
"name": "why_not",
"arguments": {
"url": "<url>"
}
}
}Most clients do this for you — see Connect a client. To drive it by hand, complete the startup lifecycle first.