Repository navigation
v0.2.0
Upgrading: a tool that fails now returns isError: true instead of a successful result whose
payload carried an error key. That covers both kinds of failure — bad input, and the Global
Meteor Network or NASA CNEOS being unreachable. Anything reading result["error"] should read the
error flag instead. The messages are unchanged.
MCP specification 2026-07-28 (#8)
- Tool errors are flagged
isError._errbuilt{"error": message}and nine call sites
returned it. It raisesToolErrornow, typedNoReturn. - Both kinds of failure are flagged, because the specification treats them the same. Bad input
(a time that cannot be read, a shower not in the IAU MDC list, a limit that is not a whole
number) and an upstream source failing. A JSON-RPC protocol error is for a request the server
cannot route at all; "an API request failure" is on the specification's own list of tool
execution errors. - This server needed two annotation blocks, and that is the point of reading each tool. Five
answer from the MDC shower list carried in the package plus geometry;meteor_activityreads the
Global Meteor Network andmeteor_fireballsreads NASA CNEOS. Fivefalse, twotrue. One
block would have advertised five closed-domain tools as open-world — or, far worse, advertised
two network calls as closed.MT-C12readsserver.pyand asserts that exactly the tools whose
bodies reachlive.are the ones publishingopenWorldHint: true, compared against the
published annotations rather than a list in the test, so moving a decorator cannot leave it
green. certifiis already correct here, and is now asserted rather than noted. This is the only
repo in the sweep where qso-graph-devel#73 applies at all:live.pybuilds its context with
ssl.create_default_context(cafile=certifi.where()).MT-C20holds that,MT-C21holds that
verification is never turned off, andMT-C22holds thatlive.pyis the only module that
reaches the network — so there is one place to get TLS right.- A failure says a source is down without describing our insides.
live.LiveErroris
deliberately vague ("the source could not be reached") and the tool adds only which source it
was.MT-C41asserts no URL, traceback or filesystem path reaches the caller — an error path is
exactly where that leaks by accident. - A test of mine could not fail, and falsifying it is what showed that.
MT-C30originally
asserted only that bad input raisedToolError. With_errreturning a payload instead of
raising, the bare call sites let execution continue and the tool crashed a few lines later —
AttributeError: 'NoneType' object has no attribute 'iau_number'— which FastMCP delivers as a
ToolErrortoo. A crash and a refusal were indistinguishable to it. It now asserts the
message each refusal was written with, andMT-C31generalises that: whatever a tool refuses, it
must not do it by leaking a Python exception. tests/test_mcp_conformance.py(MT-C01 onward, 16 tests). Every check falsified — 12 of 12 —
includingMT-C30andMT-C31against the patch that defeated the first version.- Nothing moved on the wire but the annotations, verified through a real
fastmcp.Client.
Lint (#7)
E501is adopted. 17 lines, not one a defect.- The publisher-name exemption is not needed, in the one repo where it nearly was. One line
quotes GMN's own file header verbatim —# Unique trajectory identifier; Beginning Julian date; Beginning UTC Time; IAU No; IAU code— and it splits as adjacent string literals, so the value
is byte-identical; the test that parses GMN's real format still passes. Zero exemptions, and
no# noqaanywhere in the repo. - Every tool description came out byte-identical, because none of the long lines was in a
docstring. - Falsified: a long line planted in
src/, caught.