NLWeb ask endpoint
ia.nlweb-ask · 4.26
Why it matters
NLWeb offers a site-specific answer interface through /ask and the same ask tool over MCP. This informational check observes the HTTP response and MCP tool listing; it does not execute the MCP tool or verify equivalent answers.
How to fix it
Serve NLWeb at /ask with schema.org results and expose the same ask tool over MCP.
-
Answer GET /ask?query=... with JSON that has a results array.
{"query_id": "q1", "results": [{"url": "https://example.com/shoe", "name": "Trail shoe", "schema_object": {"@type": "Product", "name": "Trail shoe"}}]} -
Give each result a schema.org object, and support streaming=false for a plain JSON answer.
-
Expose the same ask tool through a discoverable MCP server. A read-only tools/list response must include the ask tool.
Verify
curl -s 'https://{domain}/ask?query=what+does+this+site+offer&streaming=false' | jq -e '.results | length > 0'
Expected: The HTTP answer contains schema.org results. Also verify the MCP handshake and read-only tools/list response includes the ask tool. Listing the tool does not prove equivalent answers or successful execution.
Run a new scan for this checkpoint:
isagentready results {domain} --checkpoint ia.nlweb-ask
Details Mapping, lifecycle and references
- AR mapping
- Direct relation
- Evidence source
- agentready.org AR-ACT-09
- Score role
- Informational
- Introduced
- 2026-10-22
- Revised
- 2026-10-30
- Methodology version
- 2026-10-30