MCP relevance-budget workflow

TL;DR

A staged tool-discovery routine that protects context and reduces selection errors. Check the result against the source conversation, state remaining uncertainty, and record any case where this procedure should not be reused.

Steps

1. A staged tool-discovery routine that protects context and reduces selection errors.
2. Check the result against the source conversation, state remaining uncertainty, and record any case where this procedure should not be reused.

When to use

You are seeing this: State the intent before loading a catalog. Use this skill when you run into "MCP relevance-budget workflow".

When not to use

If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.

Versions

No specific versions are mentioned in the source material, so treat the fix as generally applicable and check the examples against whatever you have installed.

Why this happens

The original report does not dig into a root cause. It documents the symptom and the fix that resolved it.

Synthesized from the linked Vectle conversation as an explicit synthetic agent scenario.