Skip to content

docs(time): remove trailing comma in convert_time example response#4142

Open
abhicris wants to merge 1 commit into
modelcontextprotocol:mainfrom
abhicris:fix/time-readme-trailing-comma
Open

docs(time): remove trailing comma in convert_time example response#4142
abhicris wants to merge 1 commit into
modelcontextprotocol:mainfrom
abhicris:fix/time-readme-trailing-comma

Conversation

@abhicris
Copy link
Copy Markdown

The example response object for the convert_time tool in src/time/README.md had a trailing comma after the last key ("time_difference").

  "time_difference": "+13.0h",
}

Trailing commas are not valid in standard JSON (RFC 8259 §2), so anyone copy-pasting the example into a strict JSON parser (e.g. json.loads in Python, JSON.parse in JS, a test fixture, or a schema validator) hits a parse error on what is documented as a valid response.

Why

Looking at the git history, the trailing comma was left over when a now-removed "date_changed": true field was deleted from the example. The comma after the preceding time_difference key was never cleaned up.

This makes the README example self-consistent with how the server actually serializes responses (via pydantic/json.dumps, which never emit trailing commas).

Scope

  • Docs-only, no code touched
  • 1-line change in src/time/README.md
  • No new dependencies, no breaking changes
  • Verified the block now parses with json.loads

Types of changes

  • Documentation update

Part of open-source blockchain work from kcolbchain.com - maintained by Abhishek Krishna.

The example response object for the convert_time tool in src/time/README.md
had a trailing comma after the last key ("time_difference"). Trailing
commas are not valid in standard JSON, so anyone copy-pasting the example
into a strict JSON parser (or using it in a test fixture) hits a parse
error.

The trailing comma was left over when a now-removed 'date_changed' field
was deleted from the example; the comma after the preceding key was never
cleaned up.

This is a docs-only, 1-line change.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant