removedInput schema / $schema
Removed value: -"http://json-schema.org/draft-07/schema#"
removedInput schema / additionalProperties
Removed value: -false
changedInput schema / properties / description / description
Previous value: -"Plain-language description of the project/module about to be built — what it does, not how. The more specific, the better the match quality."New value: +"Description of what you want to build"
removedInput schema / properties / description / minLength
Removed value: -10
changedInput schema / properties / keywords / description
Previous value: -"REQUIRED: 3-4 precise search terms YOU infer from the description, using your own understanding of what the user actually means — do this especially when the description is vague, informal, or from a non-native speaker. Pick the concrete domain noun a maintainer would actually put in their README, not a generic category word: e.g. for 'thing that checks my code doesn't have secret keys by mistake' prefer [\"git\", \"secrets\", \"detect\", \"leak\"] over [\"secret\", \"scanner\", \"detect\", \"git\"] — 'scanner' is broad enough to pull in unrelated security-tool listicles, while 'leak'/'secrets' matches how gitleaks/trufflehog actually describe themselves. Avoid generic tooling-ecosystem words (mcp, agent, server, tool, app) unless the description has nothing more specific — they return noise (awesome-lists, unrelated MCP servers) rather than real competitors. Critically, favor the word a maintainer would use to describe WHAT THE TOOL IS over the word describing the USER'S PROBLEM: a real 'pretty JSON in the terminal' tool likely calls itself a 'viewer' or 'processor', not a 'pretty-printer'/'colorizer'; a real static-site link checker likely says it validates 'rendered HTML', not 'static site alt-text'. If your first guess doesn't match, mentally simulate the README of the tool you're picturing and pull words straight from that sentence."New value: +"Optional search keywords"
removedInput schema / properties / keywords / items
Removed value: -{
- "type": "string"
-}
removedInput schema / properties / keywords / maxItems
Removed value: -6
removedInput schema / properties / keywords / minItems
Removed value: -3
addedInput schema / properties / keywords / oneOf
Added value: +[
+ {
+ "items": {
+ "type": "string"
+ },
+ "type": "array"
+ },
+ {
+ "type": "string"
+ }
+]
removedInput schema / properties / keywords / type
Removed value: -"array"
removedInput schema / properties / queries / additionalProperties
Removed value: -false
changedInput schema / properties / queries / description
Previous value: -"Optional high-quality intent inferred semantically by the calling agent: category names what this is, outcome says what it accomplishes, synonyms supplies distinct terminology maintainers or product makers may use, constraints supplies up to 8 must-have properties, priorities supplies up to 4 ordered preferences, and artifactType says whether the desired result is an application, hosted service, CLI, or library. Older callers may omit these optional fields; the server will infer conservative fallbacks."New value: +"RECOMMENDED: 2-4 distinct technical search queries / keywords maintainers would use (e.g. ['gnome speech to text', 'gnome whisper dictation', 'linux offline voice typing'])."
addedInput schema / properties / queries / items
Added value: +{
+ "type": "string"
+}
removedInput schema / properties / queries / properties
Removed value: -{
- "artifactType": {
- "enum": [
- "application",
- "service",
- "cli",
- "library"
- ],
- "type": "string"
- },
- "category": {
- "minLength": 2,
- "type": "string"
- },
- "constraints": {
- "items": {
- "minLength": 2,
- "type": "string"
- },
- "maxItems": 8,
- "type": "array"
- },
- "outcome": {
- "minLength": 2,
- "type": "string"
- },
- "priorities": {
- "description": "Ordered preferences from most important to least important, such as [\"Android\", \"iOS\"]. Both can appear in results, but earlier entries receive more ranking weight.",
- "items": {
- "minLength": 2,
- "type": "string"
- },
- "maxItems": 4,
- "type": "array"
- },
- "synonyms": {
- "minLength": 2,
- "type": "string"
- }
-}
removedInput schema / properties / queries / required
Removed value: -[
- "category",
- "outcome",
- "synonyms"
-]
changedInput schema / properties / queries / type
Previous value: -"object"New value: +"array"
addedInput schema / properties / query
Added value: +{
+ "description": "Search query or project description",
+ "type": "string"
+}
removedInput schema / required
Removed value: -[
- "description",
- "keywords"
-]
