crosscheck-mcp 0.1.0 → 0.1.2
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/node-stdio.cjs +386 -69
- package/dist/node-stdio.cjs.map +1 -1
- package/dist/node-stdio.d.cts +10 -0
- package/dist/node-stdio.d.ts +10 -0
- package/dist/node-stdio.js +386 -69
- package/dist/node-stdio.js.map +1 -1
- package/dist/pricing.json +90 -0
- package/package.json +2 -1
package/dist/node-stdio.d.cts
CHANGED
|
@@ -376,6 +376,16 @@ interface SendArgs {
|
|
|
376
376
|
* picker (see core/retarget.ts) to route a node to a cheaper model
|
|
377
377
|
* without mutating the provider's default. */
|
|
378
378
|
modelOverride?: string;
|
|
379
|
+
/** F4b: optional JSON Schema that the response MUST conform to.
|
|
380
|
+
* When set, provider adapters that support native structured output
|
|
381
|
+
* (currently: openai-compatible adapter with provider=openai) wire
|
|
382
|
+
* it into the request as `response_format: {type: "json_schema"}`
|
|
383
|
+
* or the provider's equivalent. Adapters that don't support native
|
|
384
|
+
* structured mode silently ignore this field — the schema-in-prompt
|
|
385
|
+
* + F4c tolerant parser path still works as the universal fallback.
|
|
386
|
+
* Mirror of OpenAI's json_schema spec; downstream adapters normalise
|
|
387
|
+
* to their own provider's native shape. */
|
|
388
|
+
jsonSchema?: Record<string, unknown>;
|
|
379
389
|
}
|
|
380
390
|
/** Provider adapter. */
|
|
381
391
|
interface Provider {
|
package/dist/node-stdio.d.ts
CHANGED
|
@@ -376,6 +376,16 @@ interface SendArgs {
|
|
|
376
376
|
* picker (see core/retarget.ts) to route a node to a cheaper model
|
|
377
377
|
* without mutating the provider's default. */
|
|
378
378
|
modelOverride?: string;
|
|
379
|
+
/** F4b: optional JSON Schema that the response MUST conform to.
|
|
380
|
+
* When set, provider adapters that support native structured output
|
|
381
|
+
* (currently: openai-compatible adapter with provider=openai) wire
|
|
382
|
+
* it into the request as `response_format: {type: "json_schema"}`
|
|
383
|
+
* or the provider's equivalent. Adapters that don't support native
|
|
384
|
+
* structured mode silently ignore this field — the schema-in-prompt
|
|
385
|
+
* + F4c tolerant parser path still works as the universal fallback.
|
|
386
|
+
* Mirror of OpenAI's json_schema spec; downstream adapters normalise
|
|
387
|
+
* to their own provider's native shape. */
|
|
388
|
+
jsonSchema?: Record<string, unknown>;
|
|
379
389
|
}
|
|
380
390
|
/** Provider adapter. */
|
|
381
391
|
interface Provider {
|