# Learning Resource Finder: project brief

## Learner problem
A learner wants a resource on a chosen topic that fits a specific amount of study time.

## Tool contract
- Tool: `find_resources`
- Inputs: nonblank topic string, 1–80 characters; integer max_minutes, 1–120, default 30.
- Matching: case-insensitive substring in title, plus duration at or below the limit.
- Output: `demo: true`, count, and resources with stable IDs, title, minutes and format.
- Empty result: success with count 0 and an empty array.
- Invalid input: explicit tool error.
- Side effects: none. Never enrolls, buys or writes a record.

## Definition of done
- [ ] A client discovers the named tool and its input schema.
- [ ] Known searches return exact expected IDs.
- [ ] Time boundaries are respected.
- [ ] Missing, blank and incorrectly typed inputs fail clearly.
- [ ] The full stdio test passes.
- [ ] An assistant's answer matches the actual tool result.
- [ ] A classmate can reproduce the setup.

## My extension
User need:
New contract behavior:
One normal example:
One empty or boundary example:
One invalid example:
Expected output fields:
Implementation change:
Test evidence:

## Portfolio explanation
Problem:
Why MCP fits:
How the contract prevents ambiguity:
A defect I found and fixed:
A limitation still present:
Reproduction commands:
