@anuma/sdk 6.16.0 → 6.17.1

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.
@@ -32502,12 +32502,14 @@ var DEFAULT_SERVER_TOOLS_MATCH_OPTIONS = {
32502
32502
  };
32503
32503
  var SERVER_TOOL_DEPENDENCY_SETS = [
32504
32504
  {
32505
- // search finds links; reading them is always the next step.
32506
- name: "jina-research",
32505
+ // search finds links; reading them is always the next step. The reader now
32506
+ // lives on the search server — Jina's read_url / parallel_read_url were
32507
+ // removed in favour of anuma_scrape_url, which takes a batch of URLs — so
32508
+ // this edge deliberately spans two MCP servers.
32509
+ name: "web-research",
32507
32510
  members: [
32508
32511
  "AnumaJinaMCP-search_web",
32509
- "AnumaJinaMCP-read_url",
32510
- "AnumaJinaMCP-parallel_read_url",
32512
+ "AnumaSearchMCP-anuma_scrape_url",
32511
32513
  "AnumaJinaMCP-parallel_search_web"
32512
32514
  ],
32513
32515
  anchors: ["AnumaJinaMCP-search_web"],
@@ -3198,7 +3198,7 @@ interface CreateServerToolsFilterOptions {
3198
3198
  * toolSets: [
3199
3199
  * {
3200
3200
  * name: "research",
3201
- * members: ["AnumaJinaMCP-search_web", "AnumaJinaMCP-read_url", ...],
3201
+ * members: ["AnumaJinaMCP-search_web", "AnumaSearchMCP-anuma_scrape_url", ...],
3202
3202
  * anchors: ["AnumaJinaMCP-search_web"],
3203
3203
  * anchorMinSimilarity: 0.7,
3204
3204
  * },
@@ -3237,7 +3237,7 @@ declare const DEFAULT_SERVER_TOOLS_MATCH_OPTIONS: ToolMatchOptions;
3237
3237
  * These exist because semantic selection structurally cannot reach a tool
3238
3238
  * whose job is step 2 of a call-chain. Measured against the live catalog
3239
3239
  * (June 2026): on "research the latest news on X", `search_web` scores 0.64
3240
- * but `parallel_read_url` scores 0.33 and `parallel_search_web` 0.47 — below
3240
+ * but the readers score 0.33 and `parallel_search_web` 0.47 — below
3241
3241
  * the 0.5 floor, unreachable at ANY match limit. No threshold or limit tuning
3242
3242
  * fixes this; an explicit edge is the only mechanism that does.
3243
3243
  *
@@ -3198,7 +3198,7 @@ interface CreateServerToolsFilterOptions {
3198
3198
  * toolSets: [
3199
3199
  * {
3200
3200
  * name: "research",
3201
- * members: ["AnumaJinaMCP-search_web", "AnumaJinaMCP-read_url", ...],
3201
+ * members: ["AnumaJinaMCP-search_web", "AnumaSearchMCP-anuma_scrape_url", ...],
3202
3202
  * anchors: ["AnumaJinaMCP-search_web"],
3203
3203
  * anchorMinSimilarity: 0.7,
3204
3204
  * },
@@ -3237,7 +3237,7 @@ declare const DEFAULT_SERVER_TOOLS_MATCH_OPTIONS: ToolMatchOptions;
3237
3237
  * These exist because semantic selection structurally cannot reach a tool
3238
3238
  * whose job is step 2 of a call-chain. Measured against the live catalog
3239
3239
  * (June 2026): on "research the latest news on X", `search_web` scores 0.64
3240
- * but `parallel_read_url` scores 0.33 and `parallel_search_web` 0.47 — below
3240
+ * but the readers score 0.33 and `parallel_search_web` 0.47 — below
3241
3241
  * the 0.5 floor, unreachable at ANY match limit. No threshold or limit tuning
3242
3242
  * fixes this; an explicit edge is the only mechanism that does.
3243
3243
  *
@@ -8667,12 +8667,14 @@ var DEFAULT_SERVER_TOOLS_MATCH_OPTIONS = {
8667
8667
  };
8668
8668
  var SERVER_TOOL_DEPENDENCY_SETS = [
8669
8669
  {
8670
- // search finds links; reading them is always the next step.
8671
- name: "jina-research",
8670
+ // search finds links; reading them is always the next step. The reader now
8671
+ // lives on the search server — Jina's read_url / parallel_read_url were
8672
+ // removed in favour of anuma_scrape_url, which takes a batch of URLs — so
8673
+ // this edge deliberately spans two MCP servers.
8674
+ name: "web-research",
8672
8675
  members: [
8673
8676
  "AnumaJinaMCP-search_web",
8674
- "AnumaJinaMCP-read_url",
8675
- "AnumaJinaMCP-parallel_read_url",
8677
+ "AnumaSearchMCP-anuma_scrape_url",
8676
8678
  "AnumaJinaMCP-parallel_search_web"
8677
8679
  ],
8678
8680
  anchors: ["AnumaJinaMCP-search_web"],
@@ -2068,12 +2068,14 @@ var DEFAULT_SERVER_TOOLS_MATCH_OPTIONS = {
2068
2068
  };
2069
2069
  var SERVER_TOOL_DEPENDENCY_SETS = [
2070
2070
  {
2071
- // search finds links; reading them is always the next step.
2072
- name: "jina-research",
2071
+ // search finds links; reading them is always the next step. The reader now
2072
+ // lives on the search server — Jina's read_url / parallel_read_url were
2073
+ // removed in favour of anuma_scrape_url, which takes a batch of URLs — so
2074
+ // this edge deliberately spans two MCP servers.
2075
+ name: "web-research",
2073
2076
  members: [
2074
2077
  "AnumaJinaMCP-search_web",
2075
- "AnumaJinaMCP-read_url",
2076
- "AnumaJinaMCP-parallel_read_url",
2078
+ "AnumaSearchMCP-anuma_scrape_url",
2077
2079
  "AnumaJinaMCP-parallel_search_web"
2078
2080
  ],
2079
2081
  anchors: ["AnumaJinaMCP-search_web"],
@@ -473,7 +473,7 @@ declare function applyToolSets(matchedNames: Set<string>, availableNames: Set<st
473
473
  * precision.
474
474
  *
475
475
  * Use this for server-side toolkit suites where the LLM needs the full
476
- * call chain (e.g. search_web → read_url / parallel_read_url, or
476
+ * call chain (e.g. search_web → anuma_scrape_url, or
477
477
  * geocoding before the OpenMeteo data tools). Differs from `applyToolSets`,
478
478
  * which replaces non-set matches when a set activates.
479
479
  *
@@ -555,7 +555,7 @@ interface CreateServerToolsFilterOptions {
555
555
  * toolSets: [
556
556
  * {
557
557
  * name: "research",
558
- * members: ["AnumaJinaMCP-search_web", "AnumaJinaMCP-read_url", ...],
558
+ * members: ["AnumaJinaMCP-search_web", "AnumaSearchMCP-anuma_scrape_url", ...],
559
559
  * anchors: ["AnumaJinaMCP-search_web"],
560
560
  * anchorMinSimilarity: 0.7,
561
561
  * },
@@ -594,7 +594,7 @@ declare const DEFAULT_SERVER_TOOLS_MATCH_OPTIONS: ToolMatchOptions;
594
594
  * These exist because semantic selection structurally cannot reach a tool
595
595
  * whose job is step 2 of a call-chain. Measured against the live catalog
596
596
  * (June 2026): on "research the latest news on X", `search_web` scores 0.64
597
- * but `parallel_read_url` scores 0.33 and `parallel_search_web` 0.47 — below
597
+ * but the readers score 0.33 and `parallel_search_web` 0.47 — below
598
598
  * the 0.5 floor, unreachable at ANY match limit. No threshold or limit tuning
599
599
  * fixes this; an explicit edge is the only mechanism that does.
600
600
  *
@@ -473,7 +473,7 @@ declare function applyToolSets(matchedNames: Set<string>, availableNames: Set<st
473
473
  * precision.
474
474
  *
475
475
  * Use this for server-side toolkit suites where the LLM needs the full
476
- * call chain (e.g. search_web → read_url / parallel_read_url, or
476
+ * call chain (e.g. search_web → anuma_scrape_url, or
477
477
  * geocoding before the OpenMeteo data tools). Differs from `applyToolSets`,
478
478
  * which replaces non-set matches when a set activates.
479
479
  *
@@ -555,7 +555,7 @@ interface CreateServerToolsFilterOptions {
555
555
  * toolSets: [
556
556
  * {
557
557
  * name: "research",
558
- * members: ["AnumaJinaMCP-search_web", "AnumaJinaMCP-read_url", ...],
558
+ * members: ["AnumaJinaMCP-search_web", "AnumaSearchMCP-anuma_scrape_url", ...],
559
559
  * anchors: ["AnumaJinaMCP-search_web"],
560
560
  * anchorMinSimilarity: 0.7,
561
561
  * },
@@ -594,7 +594,7 @@ declare const DEFAULT_SERVER_TOOLS_MATCH_OPTIONS: ToolMatchOptions;
594
594
  * These exist because semantic selection structurally cannot reach a tool
595
595
  * whose job is step 2 of a call-chain. Measured against the live catalog
596
596
  * (June 2026): on "research the latest news on X", `search_web` scores 0.64
597
- * but `parallel_read_url` scores 0.33 and `parallel_search_web` 0.47 — below
597
+ * but the readers score 0.33 and `parallel_search_web` 0.47 — below
598
598
  * the 0.5 floor, unreachable at ANY match limit. No threshold or limit tuning
599
599
  * fixes this; an explicit edge is the only mechanism that does.
600
600
  *
@@ -1947,12 +1947,14 @@ var DEFAULT_SERVER_TOOLS_MATCH_OPTIONS = {
1947
1947
  };
1948
1948
  var SERVER_TOOL_DEPENDENCY_SETS = [
1949
1949
  {
1950
- // search finds links; reading them is always the next step.
1951
- name: "jina-research",
1950
+ // search finds links; reading them is always the next step. The reader now
1951
+ // lives on the search server — Jina's read_url / parallel_read_url were
1952
+ // removed in favour of anuma_scrape_url, which takes a batch of URLs — so
1953
+ // this edge deliberately spans two MCP servers.
1954
+ name: "web-research",
1952
1955
  members: [
1953
1956
  "AnumaJinaMCP-search_web",
1954
- "AnumaJinaMCP-read_url",
1955
- "AnumaJinaMCP-parallel_read_url",
1957
+ "AnumaSearchMCP-anuma_scrape_url",
1956
1958
  "AnumaJinaMCP-parallel_search_web"
1957
1959
  ],
1958
1960
  anchors: ["AnumaJinaMCP-search_web"],
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@anuma/sdk",
3
- "version": "6.16.0",
3
+ "version": "6.17.1",
4
4
  "description": "",
5
5
  "main": "./dist/index.cjs",
6
6
  "module": "./dist/index.mjs",