@jaypie/mcp 0.8.168 → 0.8.170
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/dist/assets.js
CHANGED
|
@@ -55,11 +55,11 @@ function getMcpAssetPaths() {
|
|
|
55
55
|
*/
|
|
56
56
|
function getMcpBuildInfo() {
|
|
57
57
|
return {
|
|
58
|
-
commit: "
|
|
58
|
+
commit: "bd4bdb10"
|
|
59
59
|
,
|
|
60
|
-
version: "0.8.
|
|
60
|
+
version: "0.8.170"
|
|
61
61
|
,
|
|
62
|
-
versionString: "@jaypie/mcp@0.8.
|
|
62
|
+
versionString: "@jaypie/mcp@0.8.170#bd4bdb10"
|
|
63
63
|
,
|
|
64
64
|
};
|
|
65
65
|
}
|
package/package.json
CHANGED
|
@@ -0,0 +1,13 @@
|
|
|
1
|
+
---
|
|
2
|
+
version: 0.6.13
|
|
3
|
+
date: 2026-09-23
|
|
4
|
+
summary: destroyTable() without a tableName throws ConfigurationError instead of a destructuring TypeError
|
|
5
|
+
---
|
|
6
|
+
|
|
7
|
+
## Changes
|
|
8
|
+
|
|
9
|
+
- **`destroyTable` fails clearly** (#582). Calling `destroyTable()` with no
|
|
10
|
+
arguments, or with an empty `tableName`, throws a `ConfigurationError`
|
|
11
|
+
before any AWS call. It previously died on destructuring with a raw
|
|
12
|
+
`TypeError`. `tableName` still has no default: deleting a table must name
|
|
13
|
+
it explicitly.
|
|
@@ -0,0 +1,16 @@
|
|
|
1
|
+
---
|
|
2
|
+
version: 1.3.49
|
|
3
|
+
date: 2026-09-24
|
|
4
|
+
summary: COST prices nemotron-lightning-3p5-30b-a3b; the model is not cataloged because it does not support tools or structured output
|
|
5
|
+
---
|
|
6
|
+
|
|
7
|
+
## Changes
|
|
8
|
+
|
|
9
|
+
- `COST` prices `accounts/fireworks/models/nemotron-lightning-3p5-30b-a3b` at $0.05 input, $0.20 output, $0.01 cache read per million tokens (Fireworks standard serverless rates)
|
|
10
|
+
- `MODEL.FIREWORKS.NEMOTRON_LIGHTNING` is deliberately absent. The model does not support tools or structured output: a `json_schema` `response_format` hangs with no response, and after a tool call it answers in prose. A caller can still pass the id directly
|
|
11
|
+
- `MODEL.FIREWORKS.NEMOTRON` remains `nemotron-3-ultra-nvfp4`, the newest serverless Nemotron Ultra
|
|
12
|
+
|
|
13
|
+
## Testing
|
|
14
|
+
|
|
15
|
+
- `npm run test -w packages/llm`: unit suite passes; Google hot specs failed on provider "high demand" 503s
|
|
16
|
+
- Live, 2026-09-24 (`APP_MODELS=accounts/fireworks/models/nemotron-lightning-3p5-30b-a3b npm run test:llm:matrix`, twice): plain and temperature passed; tools, structured, and both timed out at 180s
|
|
@@ -0,0 +1,10 @@
|
|
|
1
|
+
---
|
|
2
|
+
version: 0.8.169
|
|
3
|
+
date: 2026-09-23
|
|
4
|
+
summary: dynamodb skill notes destroyTable throws ConfigurationError when tableName is missing
|
|
5
|
+
---
|
|
6
|
+
|
|
7
|
+
## Changes
|
|
8
|
+
|
|
9
|
+
- **`dynamodb` skill**: the `destroyTable` row states that a missing
|
|
10
|
+
`tableName` throws `ConfigurationError` (#582).
|
package/skills/dynamodb.md
CHANGED
|
@@ -77,7 +77,7 @@ Schema-agnostic table operations that honor the `initClient` config (real AWS or
|
|
|
77
77
|
| `scanTable({ tableName?, pageSize? })` | Async generator yielding every raw item via a full `Scan` (paginates internally). Reads any table regardless of GSI shape -- pass the old table during a rebuild. |
|
|
78
78
|
| `countTable({ tableName? })` | Total item count via paginated `COUNT` scan (validation) |
|
|
79
79
|
| `createTable({ tableName?, billingMode?, wait? })` | Create a table with the registered-model GSI schema; waits until `ACTIVE` by default |
|
|
80
|
-
| `destroyTable({ tableName })` | Delete a table; `tableName` required (no default) |
|
|
80
|
+
| `destroyTable({ tableName })` | Delete a table; `tableName` required (no default; throws `ConfigurationError` when missing) |
|
|
81
81
|
|
|
82
82
|
### Constants
|
|
83
83
|
|