/ is the MCP list — one full-width row per tracked server.
Thirty days, because that is what the overview opens on, and both figures say so on the row.
It was seven, and the same server then read 2,027 calls at 84% on the row and 3,680 at 86% one click in — two correct answers to two different questions, with only the calls column carrying a window. Nobody reads that as two windows; they read it as the list being out of date, and they are right to, because nothing on the row said otherwise. The row is the page’s opening figure, so clicking through has to confirm it.
It refreshes like every other panel
Both figures come fromtool_hours, so this page polls on the same 30-second metrics cadence as the overview. It was the one screen that did not: the home page held numbers that went stale the moment it loaded, while the overview one click in refreshed itself — two answers to is this current about the same server.
A row does one thing
Clicking a row opens the MCP. There is nothing else on it. Renaming, keys and deletion all live inside the MCP, which means there is nothing destructive sitting beside the link people click all day — and one place to change each rather than two.Zero is an answer
A server that has never been called shows0 and 0%, not a dash and not an empty state. Nothing recorded reads as zero, never as “not yet”: a complete answer of nothing happened is worth more than a shrug.
The one exception is a genuinely unknown figure. First-call success is computed by the nightly pass, so an MCP whose only calls arrived today has calls but no rate yet — that reads as not yet computed, because a zero there would claim every call failed.