Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

T4 - add request metadata, result type, cache hints, error codes, discover schemas types

Closed
  • Is something wrong?
#242 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
30/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
scala
Domain
api, backend

Research direction

Read the linked 2026-07-28 specification sections first, then locate the existing result, capability, error, and schema-test types in the Scala project. Implement the listed metadata, result, caching, discovery, error, and extension additions, and add schema test cases for each type against the 2026-07-28 schema.

Written by the indexing model from the issue text.

Description

2026-07-28 version support

Target branch: 2026-07-28-protocol-support

  • MetaKeys object with the reserved _meta keys (progressToken, io.modelcontextprotocol/protocolVersion,
    clientInfo, clientCapabilities, logLevel, subscriptionId, serverInfo, traceparent, tracestate,
    baggage) and helpers to read and write typed values in Option[Map[String, Json]].
  • ResultType (Complete, InputRequired, Other(String)) and resultType: Option[ResultType] on every result type.
  • CacheScope (Public, Private) and ttlMs, cacheScope on ListToolsResponse, ListPromptsResult,
    ListResourcesResult, ListResourceTemplatesResult, ReadResourceResult.
  • DiscoverParams and DiscoverResult for server/discover.
  • Error codes -32020, -32021, -32022 with typed data (supported, requested, requiredCapabilities).
  • extensions: Option[Map[String, Json]] on ClientCapabilities and ServerCapabilities.
  • Schema test cases for each type against the 2026-07-28 schema.

Spec:

Conformance scenarios that must pass after this task: none.

Docs: no.

Dominant language
Scala
Stars
102
Forks
10
Avg merge
2d 6h
Merged PRs (30d)
19

Getting set up

Open in Codespaces

Starts the project's dev container in your browser, under your own GitHub account.

  • No Dockerfile or Docker Compose file
  • No pull request template
  • No contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from softwaremill/chimp

All issues in softwaremill/chimp

Similar issues

More Scala issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.