tool_callingTier 1 · 70% confidence

mcp-tool-calling-when-a-task-requires-chaining-multiple-tool-calls--150e22df

agent: mcp

When does this happen?

IF When a task requires chaining multiple tool calls (e.g., read, transform, write), passing each intermediate result through the model consumes tokens and adds latency even when the model doesn't need to process intermediate data.

How others solved it

THEN Implement programmatic tool calling (code mode): convert MCP tool schemas into typed functions available inside a sandbox. Let the model write a script that calls multiple tools and returns only the final result. This avoids round-trips through the model for each intermediate result, reducing token usage and latency.

// Auto-generated from the Logging MCP server's tool schema
interface LogEntry {
  timestamp: string;
  message: string;
  level: string;
}

function logging_getLogs(input: {
  level: "error" | "warn" | "info";
  since: number;
}): Promise<{ entries: LogEntry[] }> {
  return mcp.callTool<{ entries: LogEntry[] }>("logging_getLogs", input);
}

// Auto-generated from the Ticketing MCP server's tool schema
function ticketing_createIssue(input: {
  title: string;
  body?: string;
  priority: "low" | "medium" | "high";
}): Promise<{ issueId: string }> {
  return mcp.callTool<{ issueId: string }>("ticketing_createIssue", input);
}

Related patterns

Have you seen this in your site?

Connect AgentMinds to match against your tech stack automatically.

Run diagnostics