/** * Jira tools exposed to the coding agent — `jira_get_issue` for reads and * `jira_create_comment` for posting findings back to the issue, matching the * Linear tool surface. * * Wired into the agent through the SDK's async `extraTools` provider: on each * tool-set resolution we map the session's resourceId (the factory project * id) to its owning org and only expose the Jira tools for real factory * projects with an active Platform-managed Jira connection. * * Tenancy mirrors the Jira API routes: nothing is exposed without the host * auth seam, and the session must resolve to an org-owned project. */ import type { RequestContext } from '@mastra/core/request-context'; import type { PlatformJiraIntegration } from './integration.js'; declare function createJiraGetIssueTool(jira: PlatformJiraIntegration): import("@mastra/core/tools").Tool<{ issue: string; }, unknown, unknown, unknown, import("@mastra/core/tools").ToolExecutionContext, "jira_get_issue", unknown>; declare function createJiraCommentTool(jira: PlatformJiraIntegration): import("@mastra/core/tools").Tool<{ issue: string; body: string; }, unknown, unknown, unknown, import("@mastra/core/tools").ToolExecutionContext, "jira_create_comment", unknown>; /** * Async `extraTools` provider: expose the Jira tools only when the host runs * with web auth and the session's resource is an org-owned factory project. * * Intake source bindings scope the board feed; both tools resolve the issue * through one of the organization's active Platform Jira connections. */ export declare function buildPlatformJiraAgentTools({ requestContext, jira, }: { requestContext: RequestContext; /** The integration instance providing the Jira API client. */ jira: PlatformJiraIntegration; }): Promise | ReturnType>>; export {}; //# sourceMappingURL=agent-tools.d.ts.map