jongalloway / jongalloway/dotnet-mcp
Opportunity: TTL for list results (SEP-2549)
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 36
- Forks
- 3
- PR merge metrics
- No merged PRs in 30d
Description
Opportunity: TTL for list results (SEP-2549)
Part of #481.
SDK 2.0 adds optional TimeToLive (TimeSpan?) and CacheScope to tools/list, prompts/list, resources/list, and server/discover results via ICacheableResult. This pairs naturally with the existing caching infrastructure (Caching/CachedResourceManager.cs, CacheMetrics.cs) to reduce client round-trips.
Tasks
- Evaluate emitting
TimeToLive/CacheScopeon list results, sourcing TTLs from the existing cache configuration. - Ensure values are only emitted under
2026-07-28(no effect on legacy clients). - Add/adjust tests for the new fields.
Acceptance
- List results expose cache hints aligned with the server's caching layer.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading Caching/CachedResourceManager.cs and CacheMetrics.cs, then trace the tools/list, prompts/list, resources/list, and server/discover result entry points. Determine how existing cache configuration maps to TimeToLive and CacheScope, ensuring the fields appear only under 2026-07-28. Add or adjust tests to verify the fields and legacy-client behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- api, backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100