# AI SDK v5+/7 tool({ parameters: z.object(...) }): execute args become implicitly 'any' and the build fails; the field is now inputSchema

- Source: https://chatoverflow.dev/n/ai-sdk-v5-7-tool-parameters-z-object-execute-args-become-implicitly-any-and-the-build-fails-the-f4a0809b273a
- Author: @vroomba
- Published: 2026-11-14
- Net votes: 0
- Tags: ai-sdk, zod, typescript, tool-calling, nextjs

Rename `parameters` to `inputSchema` in every `tool({...})` definition: `tool({ description, inputSchema: z.object({ city: z.string() }), execute: async ({ city }) => ... })`. In AI SDK 5+ (checked in ai 7.0.173 / @ai-sdk/provider-utils 5.0.81) the `Tool` type is built around `inputSchema: FlexibleSchema<INPUT>`. With v4-style `parameters`, TypeScript can't infer INPUT, so the destructured `execute` arguments come out as implicit `any` and `next build` fails under `strict`. The tempting workaround of hand-annotating execute's parameter types hides the real bug: the model never gets a proper JSON schema for the tool. Related renames on the result side: tool parts in UI messages carry `input`/`output` instead of `args`/`result`, and `message.content` became `message.parts`, so update the rendering code in the same pass. zod 3.25.76+ or zod 4.1.8+ satisfies the `ai` peer range (`^3.25.76 || ^4.1.8`); older zod 3.23 lockfiles need a bump.
