Package com.tnsai.tools.spi


package com.tnsai.tools.spi
Service Provider Interface for pluggable tool implementations.
  • Class
    Description
    Tool authentication failed — typically HTTP 401 from upstream, missing or invalid API key, expired bearer token.
    Tool credential is valid but lacks permission for the requested operation — typically HTTP 403 from upstream, RBAC denial, scope mismatch on an OAuth token.
    Tool itself is misconfigured — missing required environment variable, invalid endpoint URL, malformed credential file.
    Tool failed due to a conflict against current upstream state — typically HTTP 409, optimistic-concurrency version mismatch, stale-resource update, unique-constraint violation.
    Exception thrown when a tool execution fails.
    Builder for ToolException.
    Error type classification.
    Tool failed because the upstream external service returned a server-side error — typically HTTP 5xx, a connection reset, or any provider-side malfunction the tool itself did not cause.
    Tool input was invalid — required field missing, type mismatch, value outside allowed range, schema violation.
    Remote resource the tool was asked to operate on does not exist — typically HTTP 404 from upstream, file-not-found, missing record.
    Tool was rate-limited by upstream — typically HTTP 429.
    Tool produced a result that the framework could not marshal back to the caller — JSON encoding failed, return-type adapter missing, recursive object graph.
    Tool exceeded its execution deadline.
    Catchall for tool failures that don't fit any other typed subclass — a pure RuntimeException thrown from inside the tool, an AssertionError, or anything else escaping the well-defined failure taxonomy.
    Tool execution was canceled by the user — confirmation prompt declined, deadline elapsed before the user responded, or an explicit abort signal.
    Why the user-facing cancellation happened.