token_time_bridge
Convert an LLM token budget into an estimated wall-clock time using model-specific calibration for reasoning depth and tool-call latency.
Instructions
Map LLM token budgets to estimated wall-clock time.
Uses model-specific calibration data (tokens/second, reasoning overhead, tool-call latency) to estimate how long a task will actually take. Bridges the gap between token-space (how agents reason) and time-space (what humans need). Use token_cost_estimate instead when dollar cost matters too.
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"tokens": "<tokens>",
"model": "<model>"
},
"name": "token_time_bridge"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| model | Yes | LLM model identifier. Unknown models fall back to generic estimates. | |
| tokens | Yes | Total number of tokens in the LLM request (prompt + completion). | |
| project | No | Optional project/repo identifier this estimate belongs to, for cross-project analytics. | |
| task_type | No | Optional task type for feedback matching. | |
| session_id | No | Optional session identifier (minted by a calling agent/hook) used to deduplicate repeated estimate calls for the same task within a session. | |
| task_label | No | Optional free-text label identifying the task this estimate is for (e.g. an issue key or short title). Surfaced on get_pending_estimates output for triage. | |
| tool_calls | No | Number of tool calls expected in the agentic loop. Each adds overhead latency. | |
| reasoning_depth | No | Expected depth of chain-of-thought reasoning. Deep reasoning adds significant per-token latency. | moderate |