cancel_booking
Last 24 hours
Calls
Tool calls in this window that reached a tool this server has, answered or failed. Calls to tools it lacks, resource reads and prompt gets are counted in their own cards.5
62% fewer than the 24 hours before
Error rate
Failed calls out of all calls: a result the tool marked as an error, an exception it threw, or arguments refused before it ran.0%
0 failed calls
No change from the 24 hours before
Response time
How long your server took to answer, measured by the SDK inside it, so the network to the client is not included. The median is the typical call; 19 in 20 calls finish within the 95th percentile.350ms
median, 560ms at the 95th
No change from the 24 hours before
Called from
The client with the most calls, by the name it gives itself when it connects. A client can call itself anything, so the name is as reported.Claude
40% of calls, 2 other clients
Calls over time
Show the numbers
| Time | Calls | Errors |
|---|---|---|
| 1 | 0 | |
| 0 | 0 | |
| 0 | 0 | |
| 2 | 0 | |
| 0 | 0 | |
| 0 | 0 | |
| 1 | 0 | |
| 0 | 0 | |
| 0 | 0 | |
| 0 | 0 | |
| 0 | 0 | |
| 1 | 0 | |
| 0 | 0 | |
| 0 | 0 | |
| 0 | 0 | |
| 0 | 0 | |
| 0 | 0 | |
| 0 | 0 | |
| 0 | 0 | |
| 0 | 0 | |
| 0 | 0 | |
| 0 | 0 | |
| 0 | 0 | |
| 0 | 0 | |
| 0 | 0 |
Versions
This tool's calls by the server version that answered them
| Version | First seenWhen mcpspan first saw a call answered by this version, in the data still kept. | Calls | ErrorsThe share of calls that failed: an error the tool reported, an exception it threw, or arguments the server refused. Calls to names the server does not have are counted apart. | MedianHow long calls took: half of them were faster than the median. p95 under it: 95 in 100 were faster, so it shows the slow tail the median hides. |
|---|---|---|---|---|
| 1.4.2 | 3 | 0% | 398msp95 510ms | |
| 1.4.1 | 2 | 0% | 515msp95 623ms |
Response times
Calls by how long they took
Show the numbers
| Response time | Calls | Share |
|---|---|---|
| 150ms to 250ms | 0 | 0.0% |
| 250ms to 400ms | 3 | 60.0% |
| 400ms to 600ms | 1 | 20.0% |
| 600ms to 1s | 1 | 20.0% |
| 1s to 1.5s | 0 | 0.0% |
In the tool list
What its definition costs every session, and how many of those sessions used it
- DefinitionWhat the tool's name, title, description and input schema take in the model's context, read at the start of every session whether the tool is called or not. Estimated at four bytes a token; the exact count depends on the model.
- ≈ 160 tokens, 640 B
- Share of the list
- 6%
- Shown inSessions whose client was sent this tool in the list of tools, in this window.
- 67 sessions
- Used inOf the sessions shown the tool, how many called it at least once. A tool shown often and used rarely may need a clearer description, or may not be needed.
- 5 (7%)
Response size
Over 5 answers; what the client's context takes in
- Typical (median)Half of the answers were smaller than this, as compact JSON. The size is all that is measured; the content never leaves the server.
- 1.8 kB
- Large (95th percentile)95 in 100 answers were smaller. A large one fills the agent's context, and every later step pays for it.
- 2.4 kB
- Largest
- 2.4 kB
How it fails
Nothing failed in this window.
Called from
- Claude
- 2 (40%)
- Claude Code
- 2 (40%)
- ChatGPT
- 1 (20%)
Parameters agents send
Names and types only
A name the schema does not have, or one that arrives as more than one type, is usually a description the agent is misreading.
| Name | Sent as | In calls |
|---|---|---|
| reference | string | 100% |