Skip to main content
APIContext
Talk to salesStart free
Start HereGuidesConceptsCLIReferenceChangelogStatus

Set an MCP step's result as expected

When an MCP server returns what you expect, for example the right list of tools, you can mark that step's result as expected. APIContext derives a data check from it, and every later result of the same step is checked against it. A difference shows as a Data issue on the project's Conformance page.

Before you start​

  • You need an MCP monitor with a successful result.
  • You need edit access to the project. Marking a result as expected also adds a tag to the monitor.

Mark a step's result as expected​

  1. Open the MCP monitor's result, then click the step whose result you want to keep. The step opens in a sidebar.
  2. In the Baseline section, click Mark as Expected.
  3. In Check name, keep the suggested name or enter your own. If a check with that name already exists, it is replaced.
  4. Under Exclude, choose the parts of the result that are allowed to change. The options depend on the step type. For a List Tools step, for example, tool descriptions, parameter descriptions, and the paging cursor are excluded by default, because they can change without the server's behavior changing.
  5. To exclude anything else, enter JSON paths in the box, one per line, relative to the step result, for example $.tools[*].outputSchema. [*] matches every element of a list.
  6. Click Save Check.

The section confirms the saved check, how many paths it excludes, and the tag added to the monitor, in the form data-baseline:<id>. The check applies to monitors with that tag, so keep the tag on the monitor.

The Baseline section appears only on steps that act on the server and returned a result. A step that failed cannot be used as a baseline.

Accept a change as expected​

When a server changes on purpose, for example when a tool is added, the next results raise Data issues. To make the new result the expected one:

  1. On the project's Conformance page, open Issue Details and expand the Data issue. A check created from a result shows Baseline with the date it was derived.
  2. Click Accept as Expected, then Accept.

The check is derived again from that result, later results are checked against the new baseline, and the issue is marked resolved.