[GH-ISSUE #7503] [Bug] Exclusive input bounds are reported as the inclusive minimum or maximum #4462

Open
opened 2026-10-31 00:50:03 +00:00 by bsakaguchi · 0 comments
Owner

Originally created by @Adolanium on GitHub (Oct 27, 2026).
Original GitHub issue: https://github.com/morluto/rea/issues/7503

Before submitting

  • I searched the open and closed issues for a related report.
  • I removed credentials, tokens, private paths, and sensitive target data.

Area

MCP or agent integration

Observed behavior

An input that fails an exclusive bound is reported with that bound as an inclusive limit. MCP inspect_analysis_view with view: { kind: "page", collection: "sections", offset: 0, limit: 0 } returns an out_of_range issue with minimum: 0, although 0 is the rejected value. Other .positive() and .lt() inputs behave the same way.

Reproduction

Ran on Linux (WSL Ubuntu, Node 24.22.1) at upstream/main 79d2fc054 through an in-memory MCP session: the call above returns invalid_request with { path: ["view", "limit"], reason: "out_of_range", minimum: 0 }.

Expected behavior

An exclusive bound is not reported as minimum or maximum, which are inclusive. The issue keeps the bound in its message (for example ">0").

Impact and scope

An agent correcting the request can retry with the value the error says is allowed and fail again.

REA version

revision 79d2fc054

Runtime and platform

Linux (WSL Ubuntu), Node 24.22.1

Target and artifact context

Fixture analysis Evidence.

Interface

MCP

Earliest failure stage

Request parsing or validation

Relevant output or evidence

Root cause and fix are in #7502, with the regression tests.

Typed outcome or recovery expected

An out_of_range issue without an inclusive bound for an exclusive limit.

Analysis or suspected cause

Root cause and fix are in #7502.

Additional context

Fixed by #7502.

Originally created by @Adolanium on GitHub (Oct 27, 2026). Original GitHub issue: https://github.com/morluto/rea/issues/7503 ### Before submitting - [x] I searched the open and closed issues for a related report. - [x] I removed credentials, tokens, private paths, and sensitive target data. ### Area MCP or agent integration ### Observed behavior An input that fails an exclusive bound is reported with that bound as an inclusive limit. MCP `inspect_analysis_view` with `view: { kind: "page", collection: "sections", offset: 0, limit: 0 }` returns an `out_of_range` issue with `minimum: 0`, although 0 is the rejected value. Other `.positive()` and `.lt()` inputs behave the same way. ### Reproduction Ran on Linux (WSL Ubuntu, Node 24.22.1) at upstream/main 79d2fc054 through an in-memory MCP session: the call above returns `invalid_request` with `{ path: ["view", "limit"], reason: "out_of_range", minimum: 0 }`. ### Expected behavior An exclusive bound is not reported as `minimum` or `maximum`, which are inclusive. The issue keeps the bound in its message (for example ">0"). ### Impact and scope An agent correcting the request can retry with the value the error says is allowed and fail again. ### REA version revision `79d2fc054` ### Runtime and platform Linux (WSL Ubuntu), Node 24.22.1 ### Target and artifact context Fixture analysis Evidence. ### Interface MCP ### Earliest failure stage Request parsing or validation ### Relevant output or evidence Root cause and fix are in #7502, with the regression tests. ### Typed outcome or recovery expected An `out_of_range` issue without an inclusive bound for an exclusive limit. ### Analysis or suspected cause Root cause and fix are in #7502. ### Additional context Fixed by #7502.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
morluto/rea#4462
No description provided.