@trazum/mcp 1.74.0 → 1.75.0
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/README.md +7 -4
- package/package.json +2 -2
package/README.md
CHANGED
|
@@ -31,6 +31,9 @@ because "MCP server" reads like infrastructure and this is not.
|
|
|
31
31
|
| `optimize_prompt` | The shorter text, the token counts either side, what the difference is worth per month, and any advisories. |
|
|
32
32
|
| `profile_usage` | Where the money went, from a usage log passed as text: the spend split, per label and per model, whether caching paid for itself, and the levers that would actually move the bill. `label`, `since`/`until` and `previous_log` drill down and compare; `what_if` prices the same calls on another model — arithmetic, not advice, and it says so. `pricing_overlay` takes the same JSON a `--pricing` overlay file holds, as text — models it adds or overrides price the whole report, and the report says the overlay is in effect. The one tool whose figures are exact — they are the provider's own billed counts. |
|
|
33
33
|
| `list_models` | Prices, context windows and cacheable minimums, with the date the table was reviewed. |
|
|
34
|
+
| `spend_guard` | Whether the call you are about to make fits the budget — `yes`, `no`, or `cannot-tell`, with the cheaper ways to make the same call attached to a refusal. See below. |
|
|
35
|
+
| `position` | Where the month stands against every ceiling you pass, measured from the log text alone — the denominator on every figure, and no forecast anywhere. |
|
|
36
|
+
| `prompt_writer` | Interviews you, then writes the prompt. Fixed questions, your words, same answers same text — nothing is generated. |
|
|
34
37
|
|
|
35
38
|
`check_prompt` is the one worth wiring up. It has **three** outcomes rather than
|
|
36
39
|
two, and the third is the point:
|
|
@@ -79,10 +82,6 @@ samples in seven languages), and every tool says so in its own output. A prompt
|
|
|
79
82
|
within a few percent of its budget should be treated as uncertain rather than as
|
|
80
83
|
passing. `--exact-tokens` settles it against the counting endpoint, which is free.
|
|
81
84
|
|
|
82
|
-
## Licence
|
|
83
|
-
|
|
84
|
-
MIT. Part of [Trazum](https://github.com/Davmunrey/Trazum).
|
|
85
|
-
|
|
86
85
|
## `spend_guard`
|
|
87
86
|
|
|
88
87
|
Whether a call you are about to make fits the budget: `yes`, `no`, or
|
|
@@ -91,3 +90,7 @@ priced for this call, each naming what it assumes, and each already filtered to
|
|
|
91
90
|
models the prompt fits inside. The measured half (spend so far) and the
|
|
92
91
|
estimated half (the call you described) stay apart, and the verdict says which
|
|
93
92
|
it rests on. Nothing is called and nothing is spent to answer.
|
|
93
|
+
|
|
94
|
+
## Licence
|
|
95
|
+
|
|
96
|
+
MIT. Part of [Trazum](https://github.com/Davmunrey/Trazum).
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@trazum/mcp",
|
|
3
|
-
"version": "1.
|
|
3
|
+
"version": "1.75.0",
|
|
4
4
|
"description": "Trazum as an MCP server: let an agent price and budget its own prompts before it sends them.",
|
|
5
5
|
"license": "MIT",
|
|
6
6
|
"author": "David Mu\u00f1oz Rey",
|
|
@@ -37,7 +37,7 @@
|
|
|
37
37
|
"prepublishOnly": "npm run build && npm test"
|
|
38
38
|
},
|
|
39
39
|
"dependencies": {
|
|
40
|
-
"@trazum/core": "1.
|
|
40
|
+
"@trazum/core": "1.75.0"
|
|
41
41
|
},
|
|
42
42
|
"devDependencies": {
|
|
43
43
|
"@types/node": "^26.2.0",
|