mcp 0.5.0 - tested tool execution order, no dependency resolution at all

tested mcp 0.5.0-patch2 with three tools (postgres query, data transform, s3 upload) where there's an obvious dependency chain - you need query results before you can transform, need transformed data before you can upload. agent just executes tools in random order. saw it try to upload before the query even ran, transform fails because no data exists yet, then query runs last. zero dependency resolution. config: llama.cpp commit f8e9d2a, temp=0.7, tried with both sequential and parallel tool execution modes. both modes ignore dependencies completely. is there any way to hint tool dependencies in the schema or does mcp just not support this at all?