get_weather
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.46
19% 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.50%
Elevated23 failed calls
48.2 pts higher than 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.500ms
median, 2.2s at the 95th
400% slower than 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
43% of calls, 4 other clients
Calls over time
Show the numbers
| Time | Calls | Errors |
|---|---|---|
| 1 | 0 | |
| 1 | 0 | |
| 6 | 0 | |
| 0 | 0 | |
| 0 | 0 | |
| 2 | 0 | |
| 1 | 0 | |
| 0 | 0 | |
| 0 | 0 | |
| 9 | 9 | |
| 17 | 13 | |
| 3 | 0 | |
| 1 | 1 | |
| 0 | 0 | |
| 1 | 0 | |
| 1 | 0 | |
| 0 | 0 | |
| 1 | 0 | |
| 0 | 0 | |
| 0 | 0 | |
| 0 | 0 | |
| 0 | 0 | |
| 1 | 0 | |
| 1 | 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 | 38 | 61% | 774msp95 2.2s | |
| 1.4.1 | 8 | 0% | 66msp95 73ms |
Response times
Calls by how long they took
Show the numbers
| Response time | Calls | Share |
|---|---|---|
| Up to 1ms | 0 | 0.0% |
| 1ms to 2ms | 1 | 2.2% |
| 2ms to 3ms | 1 | 2.2% |
| 3ms to 5ms | 0 | 0.0% |
| 5ms to 8ms | 0 | 0.0% |
| 8ms to 12ms | 0 | 0.0% |
| 12ms to 20ms | 0 | 0.0% |
| 20ms to 30ms | 0 | 0.0% |
| 30ms to 45ms | 3 | 6.5% |
| 45ms to 65ms | 6 | 13.0% |
| 65ms to 100ms | 7 | 15.2% |
| 100ms to 150ms | 2 | 4.3% |
| 150ms to 250ms | 2 | 4.3% |
| 250ms to 400ms | 0 | 0.0% |
| 400ms to 600ms | 1 | 2.2% |
| 600ms to 1s | 7 | 15.2% |
| 1s to 1.5s | 7 | 15.2% |
| 1.5s to 2.5s | 8 | 17.4% |
| 2.5s to 4s | 1 | 2.2% |
| 4s to 6s | 0 | 0.0% |
Repeated calls
Same arguments as the call before, in the same session
13 of 46 calls (28%)
An agent sending the same call again usually did not get what it needed from the answer: an error it could not act on, or a result it did not recognise as complete. Sessions show where it happened.
Right before it went wrong
Before 26 repeated or failed calls, in their sessions
What the agent called just before get_weather repeated itself or failed. One call standing out usually did not do what the agent expected: a click that did not land, a search that came back empty.
| Called before | Client | Repeated | Failed |
|---|---|---|---|
| get_weather | Claude | 7 | 10 |
| get_weather | MCP Inspector | 3 | 4 |
| get_weather | Claude Code | 3 | 3 |
| Resource airports://{code} | MCP Inspector | 0 | 1 |
| book_flight | Claude | 0 | 1 |
| get_flight_status | Claude | 0 | 1 |
| search_flights | Other | 0 | 1 |
| seat_map | Claude Code | 0 | 1 |
| Resource trips://{id} | Claude | 0 | 1 |
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.
- ≈ 103 tokens, 410 B
- Share of the list
- 4%
- 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.
- 26 (39%)
Response size
Over 23 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.
- 549 B
- Large (95th percentile)95 in 100 answers were smaller. A large one fills the agent's context, and every later step pays for it.
- 1.0 kB
- Largest
- 1.0 kB
How it fails
23 failed
- Crashed
- 21
- Invalid arguments
- 2
What it said, most often
503 Service Unavailable from weather provider
21 times, crashed, last
Called from
- Claude
- 20 (43%)
- Claude Code
- 11 (24%)
- MCP Inspector
- 8 (17%)
- Cursor
- 3 (7%)
- Other
- 3 (7%)
Which arguments were invalid
2 calls refused before the tool ran
- city
- 2 calls
The argument agents get wrong most is usually one whose description leaves room for the wrong shape.
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 |
|---|---|---|
| city | string | 100% |