Add a Case-Details Viewer

Turn one search result into a second small, testable feature.

You will know how to ask the agent for a case-details control and test it using an ID from a real search response.

Build on the working search

Once search works, ask for one new behavior: retrieve and display the details for a specific case. This is a useful next step because it builds directly on data the app already returns.

Describe the user-facing result you want. You do not need to name the internal Descrybe function. In the video, the coding agent inspected the available tools and found the appropriate case-details operation itself.

Case-details feature prompt
Add a small case-details area to the existing app. Let me enter or paste a case ID from the concept-search results, request that case from Descrybe Legal Engine, and view the returned case details. Keep the existing connection and search controls working. After implementing it, tell me what changed, what you tested, and the exact restart or refresh steps I should follow.

Test the complete path

  1. 1Restart the app if the agent says a restart is required.
  2. 2Refresh the browser so you are viewing the latest interface.
  3. 3Connect to Descrybe again if the app is not already connected.
  4. 4Run a concept search.
  5. 5Copy a case ID from one result.
  6. 6Paste the ID into the case-details control.
  7. 7Request the details and inspect the returned fields.

Decide what to improve later

The case details may still appear as raw JSON. That is fine for the proof of concept. You now know that the app can move from a broad concept search to a particular legal source.

Later, you can ask the agent to display only the fields your users need, add a result-selection control, link search results directly to the details view, or create a source-review layout. Each of those should remain its own testable step.

Review the legal-tool behavior

  • Does the selected case match the ID you requested?
  • Are the court, date, citation, and source fields displayed accurately?
  • Can a user tell when data is missing or the request fails?
  • Does the interface preserve a path back to the underlying source?