fix(agent): align ixp extraction tool with the job attachment strategy

[radu-mocanu]

Summary

• the ixp extraction tool now generates its args schema from resource.inputSchema instead of a hardcoded flat model, so it honours the job-attachment $ref that agent builder already writes
• the tool call resolves job attachments through the shared helper, so the model passes only the attachment id and the full attachment is filled in from state
• an id that is missing from state is reported back to the model instead of reaching the sdk

Why

the ixp tool was the only attachment-carrying tool not following the shared strategy. it ignored resource.inputSchema entirely, hardcoded an alias-free mirror of Attachment, and typed the id as uuid.UUID.

that last part broke tool simulation: langchain validates arguments against args_schema before invoking the tool, so the tool received a live UUID object rather than the string the model emitted, and anything encoding those kwargs with a plain json.dumps failed with Object of type UUID is not JSON serializable.

process_tool, context_tool, deeprag_tool and analyze_files_tool all generate the schema from the resource, keep the id a string, and convert to uuid.UUID only at the sdk call site. the ixp tool now does the same, which fixes the serialization failure as a side effect of the alignment rather than as a special case.

the arg-resolution half of get_job_attachment_wrapper is extracted as resolve_job_attachment_args so the ixp wrapper can reuse it while keeping its own result handling (tools_storage plus the dataProjection tool message that ixpVsEscalation depends on).

[Copilot]

Pull request overview

Adjusts the IXP extraction tool’s attachment id handling so LangChain/Pydantic validation keeps tool kwargs JSON-native (string IDs), while still supporting existing Python callers that may pass uuid.UUID.

Changes:

• Changed ExtractionToolInputSchema.id from uuid.UUID to str, and added validation/normalization logic.
• Updated the extraction tool implementation to convert the validated string id to uuid.UUID only at the SDK boundary.
• Added/updated tests to assert schema alignment with Attachment and to ensure malformed ids fail validation.

Reviewed changes

Copilot reviewed 3 out of 4 changed files in this pull request and generated 1 comment.

File	Description
src/uipath_langchain/agent/tools/extraction_tool.py	Switches schema id to str, validates/normalizes it, and converts to uuid.UUID when calling the SDK.
tests/agent/tools/test_extraction_tool.py	Extends tests to assert the schema divergence for id, ensure parsed kwargs keep id as str, and invalid ids raise validation errors.
pyproject.toml	Bumps project version to 0.14.17.
uv.lock	Updates lockfile metadata/version to match the release bump.

[andreitava-uip]

Do we know that deployed agents with IXP tools have been migrated? or that the resource.input_schema had always been populated?

Worried we might break some old agents for which the schema in agent.json was not defined and we relied on the predefined pydantic model

[radu-mocanu]

the schema is always defined in agent builder. however seems like the CLI is scaffolding an empty schema.
added for the time being a fallback inout schema to be back compat

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
97.7% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud