NLWeb endpoint

Supporting documents: NLWeb specification

Lumar readiness bar: no specification requires this. Bad: /ask answered an anonymous query with an HTTP error, so an agent that discovers the endpoint gets an error reply (a refusal, a throttle, a failure) instead of a usable result (an application "no results"/failure at HTTP 200 is valid, not flagged). Fix: the repair depends on the status, which the Findings column names: 401/403 means answer anonymous queries or publish how an agent authenticates, 429 means let occasional anonymous queries through, and send Retry-After if you do not already, any other error means answer with HTTP 200 and an NLWeb response body.

Supporting documents: NLWeb specification

Related guidance in NLWeb specification. Bad: /ask answered, but an agent can't read the answer. Either a streamed SSE frame isn't valid JSON, or the v0.55 envelope is broken: a _meta.response_type outside the four defined values (answer, elicitation, promise, failure — the value is case-sensitive), a missing _meta.version, or a member missing or malformed (an answer with no results/structuredData, a promise with no promise.token, a failure with no error.code, an elicitation question without its id/text/type). A member v0.55 marks optional counts here when it is present with the wrong shape (elicitation.text that isn't a string, questions that isn't an array of question objects): optional licenses omitting it, not breaking it. Fix: emit each streamed event as one complete JSON object, and send a v0.55-defined response_type with _meta.version and members that are complete and well-formed; the Findings column says which applies, including both when a response manages both.

Supporting documents: NLWeb specification

Related guidance in NLWeb specification. Bad: the ask tool has no description, so an agent can't tell what it does or when to call it. Fix: give the tool a description, e.g. "Ask a natural-language question about this site's content".

Supporting documents: NLWeb specification

Related guidance in NLWeb specification. Bad: the ask tool's inputSchema declares no usable "query" property, so agents can't tell how to pass the question. Fix: declare inputSchema with a string "query" property (v0.55's query.text shape also counts).

Supporting documents: NLWeb specification

NLWeb specification permits this, so it never fails the site. Informational (does not fail nlWebRestValid): /ask returned result items but none carries Schema.org typing, which the spec recommends rather than requires. Consider attaching a schema.org object per result so agents get structured data, not prose.