Test the Connection Before Building More

List the available tools and run a concept search before adding another feature.

You will know how to prove that the app can make authenticated Descrybe requests and return legal search data.

Test the hardest dependency first

A connected-looking button is not enough. Before building more interface, make the app perform a real Descrybe request.

In the video, the prototype first lists the available tools. That quick request confirms that the app can reach Descrybe Legal Engine and receive a response through the connection you just authorized.

Run a concept search

Next, use the prototype’s search control. A concept search should return a set of cases and structured details that the application can use in later steps.

At this stage, a raw response is acceptable. The goal is not a polished search-results screen; it is proof that the legal research request works and that your app receives usable data.

What the JSON means

You may see the response displayed as JSON. JSON is a structured format designed for software to read while still being reasonably understandable to a person.

You do not need to manually interpret every field. The important point is that the response contains details the agent can later turn into cards, tables, links, filters, or another interface suited to your tool.

  • Confirm that the request finishes without an error.
  • Confirm that one or more results appear.
  • Look for stable identifiers such as a case ID.
  • Save interface improvements for a later, separate step.

Ask for a focused connection test

Tool and search test prompt
The app can now connect to Descrybe. Before adding any other features, please make sure the interface can (1) list the available Descrybe Legal Engine tools and (2) run one simple concept search and display the raw structured response. Keep this as a diagnostic interface for now. Tell me exactly how to test each request and what successful output should look like.

Do not confuse data with a conclusion

A successful API response proves that the connection and request path work. It does not prove that every returned case is relevant, current, or suitable for a legal conclusion.

Legal source selection and review remain human tasks. Later versions of the app can help make that review easier, but the prototype should never hide the source path behind a confident generated answer.