Implemented
0
Anthropic Chat Model: expose "strict": true for client tool definitions
Source: n8n-io/n8n#37914 · opened by @HanumanTFM
Environment: n8n 2.37.7, @n8n/n8n-nodes-langchain.agent typeVersion 1.9 (AgentV1), lmChatAnthropic 1.6, @langchain/anthropic 1.5.6, model claude-opus-5, adaptive thinking, streaming, prompt caching 5m, four client tools, all subworkflow-backed. Evidence comes from a transparent proxy placed between n8n and api.anthropic.com, capturing 167 exchanges and 267 tool_use blocks over a production-equivalent workload driven through the real agent loop. Problem Anthropic tool use is non-strict by default. In that mode a JSON Schema required list guides generation but does not constrain it, and the model may emit a tool call with no arguments at all. Anthropic documents strict: true as the mechanism that guarantees schema-conforming tool inputs through constrained sampling. n8n cannot send it. A source read of 2.37.7 finds no strict handling anywhere in the langchain nodes: no node parameter, no bindTools(tools, { strict: true }), no withConfig({ strict: true }). The Tools Agent only checks…
No pledges yet. Be the first to back this.
Comments
Similar requests
AI Agent: return tool-schema validation failures to the model as recoverable errors instead of terminating the execution
0 votes · 0 comments
When custom Ollama credentials are configured and the endpoint is inaccessible, the '/home/chat' page keeps displaying a loading status when selecting a model, resulting in a timeout for the API endpoint /rest/chat/models.
0 votes · 0 comments
Dynamic Multi-Action AI Tool Nodes (Unified Tool Definition for AI Agents)
0 votes · 0 comments
Bug: Agent tools lack separate caller-provided runtime context
0 votes · 0 comments
Feature request: Expose stop execution in Instance-level MCP
0 votes · 0 comments
No comments yet.