---
title: ToolRouter — Agent Use Case Guide
description: Step-by-step guide for completing a task with a specific AI agent using ToolRouter.
url: https://toolrouter.com/tools/record-collector/use-cases/identify-pressing-from-clues/copilot
---
# How to Identify a Pressing from Clues with Copilot

Determine the exact pressing of a record using catalog numbers, matrix codes, label variations, and other physical clues. Use `identify_pressing`, `edition_match`, and `release_details` to narrow down the possibilities. Copilot is a good fit when you want the identification result in a structured format you can drop into a collection database or catalog tool.

## Setup

{"mcpServers":{"toolrouter":{"command":"npx","args":["-y","toolrouter-mcp"]}}}

## Steps

1. Connect ToolRouter in Copilot: {"mcpServers":{"toolrouter":{"command":"npx","args":["-y","toolrouter-mcp"]}}}
2. Enter every physical clue: catalog number, matrix text, label design, barcode, country, and any cover or sleeve identifiers.
3. Run `identify_pressing`, `edition_match`, and `release_details` through `record-collector` to identify and confirm the pressing.
4. Ask Copilot to return the result as structured data with fields for pressing ID, edition, country, year, label variant, and confidence level.
5. Import the structured identification into your collection tracking system.

## Example Prompt

```
Use record-collector to identify a pressing. Columbia Records label, catalog PC 34987, matrix AL 34987-1A in the runout, no barcode. Run identify_pressing, edition_match, and release_details. Return structured JSON with the pressing identity and confidence level.
```

## Tips

- Standardize your clue input format across records so batch identification runs produce comparable output.
- Ask Copilot to include a confidence field so you can flag uncertain identifications for manual review.
