Repository navigation
Clarify task selection and recovery in MCP tool metadata - #8
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Agents selecting DreamLayer tools need to know the intended task, required inputs, cost and recovery action before invoking paid work. Expand all seven tool descriptions with those facts, name supported logo/product/marketing use cases, and explain rate-limit backoff and existing-job recovery. Pin README installation examples to the published sprite-capable beta.3 and link the canonical workflow repository.
Validation: all 58 MCP tests pass, including clean package installation, schemas, discovery, safe errors and interrupted-stream recovery. Live beta.3 capabilities/balance and a reference-to-sprite workflow also completed. These source metadata changes require a new npm release to reach package installations; npm authentication is currently expired. No API behavior or stable npm tag changes.