fix: update instructions for mcp

[jor2]

Description

mcp server was hallucinating there was 15 submodules in the lz-vpc instead of actually 2 based on past conversation history context.

mcp wasn't providing all the possible solutions for my problem to implement reserved ips in the example i gave it and instead just stopped at the first solution it came across with floating ip submodule implementation.

Release required?

• No release
• Patch release (x.x.X)
• Minor release (x.X.x)
• Major release (X.x.x)

Release notes content

Run the pipeline

If the CI pipeline doesn't run when you create the PR, the PR requires a user with GitHub collaborators access to run the pipeline.

Run the CI pipeline when the PR is ready for review and you expect tests to pass. Add a comment to the PR with the following text:

/run pipeline

Checklist for reviewers

• If relevant, a test for the change is included or updated with this PR.
• If relevant, documentation for the change is included or updated with this PR.

For mergers

• Use a conventional commit message to set the release level. Follow the guidelines.
• Include information that users need to know about the PR in the commit message. The commit message becomes part of the GitHub release notes.
• Use the Squash and merge option.

[daniel-butler-irl]

I read LLMs prefer positive prompting, and do, don't suggest recommendations while ALWAYS and NEVER make them hard requirements. Try and see if this makes any noticeble difference:

**ALWAYS**:

- Provide a concise, curated selection of the most relevant modules
- Explore and compare multiple alternatives before recommending
- Conduct thorough searches to ensure comprehensive coverage
- Present a single best-fit option when the use case clearly points to one solution 

[jor2]

@daniel-butler-irl okay let me try that, thank you:). Where do you do most of your reading?