melchizedek-agents 1.0.0 → 1.0.2

package/dist/lib/tools/xSearchTool.js

@@ -1,74 +0,0 @@
-/**
- * lib/tools/xSearchTool.ts — xAI X (Twitter) search, sentinel-style.
- *
- * WHY this file exists:
- *   xAI's Agent Tools API exposes `x_search` — server-side live search over
- *   X posts — as a first-class tool alongside `web_search` (verified live
- *   against api.x.ai/v1/responses, 2026-07-24). It is the one search
- *   capability no other provider offers, and the reason to route a
- *   news/social agent to a grok-* model at all.
- *
- * HOW IT WORKS (mirrors webSearchTool.ts exactly):
- *   Declaring `x_search` in an agent's YAML tools list self-registers a
- *   sentinel in llmRequest.toolsDict. _getDeclaration() returns undefined so
- *   it is never sent as a client-side function tool; the GptLlm/GrokLlm
- *   request builder calls wantsXSearch(llmRequest) and appends
- *   { type: 'x_search' } to the provider tools.
- *
- * SCOPE: xAI-only. Declare it ONLY on grok-* agents — other Responses-API
- *   providers (OpenAI) reject the unknown tool type with a 400, and Gemini/
- *   Anthropic adapters ignore the sentinel entirely (the tool degrades to a
- *   no-op there rather than throwing, same non-throwing routing contract as
- *   web_search).
- *
- * WHICH CONSTRAINTS: xAI accepts server-side search constraints on the tool
- *   object itself (verified against docs.x.ai/developers/tools/x-search,
- *   2026-08-02): from_date/to_date (YYYY-MM-DD) and allowed_x_handles/
- *   excluded_x_handles (≤20 each, mutually exclusive). They come from the
- *   environment, not YAML — XAI_X_SEARCH_FROM_DATE, XAI_X_SEARCH_TO_DATE,
- *   XAI_X_SEARCH_ALLOWED_HANDLES, XAI_X_SEARCH_EXCLUDED_HANDLES (handle
- *   lists comma-separated, leading @ tolerated) — the XAI_COLLECTION_IDS
- *   doctrine: constraints are deployment configuration, the YAML stays
- *   shareable. Misconfiguration degrades with a warning, never fatally:
- *   malformed dates are dropped, oversize handle lists truncate, and when
- *   both lists are set the allowlist wins.
- */
-import { BaseTool } from '../adkPeer.js';
-import { providerForModel } from '../models/providerMap.js';
-import { X_SEARCH_MARKER } from './nativeTools.js';
-import { NATIVE_TOOL, nativeToolMarkerOf } from './tool.js';
-export const X_SEARCH_TOOL_NAME = 'x_search';
-/** The ADK runtime's form of X_SEARCH_MARKER (lib/tools/nativeTools.ts), carrying its marker. */
-export class XSearchTool extends BaseTool {
-    [NATIVE_TOOL] = X_SEARCH_MARKER[NATIVE_TOOL];
-    constructor() {
-        super({ name: X_SEARCH_TOOL_NAME, description: X_SEARCH_MARKER.description });
-    }
-    /** Never a client-side function tool — xAI runs the search server-side. */
-    _getDeclaration() {
-        return undefined;
-    }
-    /** Server-side tool: nothing to execute locally. */
-    async runAsync() {
-        return Promise.resolve();
-    }
-    async processLlmRequest({ llmRequest }) {
-        if (!llmRequest.model)
-            return;
-        if (providerForModel(llmRequest.model) !== 'xai')
-            return; // no-op elsewhere
-        llmRequest.toolsDict[X_SEARCH_TOOL_NAME] = this;
-    }
-}
-/** Shared instance, mirroring WEB_SEARCH. */
-export const X_SEARCH = new XSearchTool();
-/** True when the agent requested X search (xAI sentinel path), by marker. */
-export function wantsXSearch(llmRequest) {
-    return isXSearchSentinel(llmRequest.toolsDict?.[X_SEARCH_TOOL_NAME]);
-}
-/** Sentinel test used by the request builder to skip function-tool emission: the x_search marker, on either form. */
-export function isXSearchSentinel(tool) {
-    return nativeToolMarkerOf(tool) === 'x_search';
-}
-/** The XAI_X_SEARCH_* reader lives in lib/tools/xaiSearchParams.ts (no @google/adk); re-exported here under its old name. */
-export { xSearchParamsFromEnv } from './xaiSearchParams.js';