docs(usability): enforce ID→name resolution in all tool docstrings (v1.4.3)
Add explicit guidance to resolve raw API IDs to human-readable names before user display. Affected tools: get_tasks, get_lists, get_activities, get_wall_posts, get_members, get_circles, get_categories, get_meal_plan. Add general usability rule to CLAUDE.md implementation section: never present raw numeric/metaIDs to the user. No breaking changes; docstring improvements only. Co-Authored-By: Claude Haiku 4.5 <noreply@anthropic.com>
This commit is contained in:
@@ -10,6 +10,25 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
|
||||
This project follows Semantic Versioning (SemVer).
|
||||
Breaking changes (removed tools, changed parameters) increment the major version.
|
||||
|
||||
## [1.4.3] – 2026-04-18
|
||||
|
||||
### Improved
|
||||
- **Usability: ID resolution in docstrings** — enforce transparent display of human-readable names:
|
||||
- `get_tasks`: Document required member/category name resolution before user display
|
||||
- `get_lists`: Document required circle name resolution before user display
|
||||
- `get_activities`: Document required author name resolution before user display
|
||||
- `get_wall_posts`: Document required author name resolution before user display
|
||||
- `get_members`: Added proactive call guidance before presenting member-ID data
|
||||
- `get_circles`: Added proactive call guidance before presenting circle-ID data
|
||||
- `get_categories`: Added proactive call guidance for shopping list tasks
|
||||
- `get_meal_plan`: Document required recipe name resolution for recipe_id before user display
|
||||
- `CLAUDE.md`: Added general usability rule at top of implementation section
|
||||
|
||||
### Notes
|
||||
- No breaking changes; docstring enhancements only
|
||||
- All tools remain backward compatible
|
||||
- Ensures consistent UX: no raw numeric/metaIDs shown to users in any context
|
||||
|
||||
## [1.4.2] – 2026-04-18
|
||||
|
||||
### Fixed
|
||||
|
||||
Reference in New Issue
Block a user