Skip to main content
Glama

token_time_bridge

Read-onlyIdempotent

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

NameRequiredDescriptionDefault
modelYesLLM model identifier. Unknown models fall back to generic estimates.
tokensYesTotal number of tokens in the LLM request (prompt + completion).
projectNoOptional project/repo identifier this estimate belongs to, for cross-project analytics.
task_typeNoOptional task type for feedback matching.
session_idNoOptional session identifier (minted by a calling agent/hook) used to deduplicate repeated estimate calls for the same task within a session.
task_labelNoOptional 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_callsNoNumber of tool calls expected in the agentic loop. Each adds overhead latency.
reasoning_depthNoExpected depth of chain-of-thought reasoning. Deep reasoning adds significant per-token latency.moderate

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv0.8.0
    • removedInput schema / additionalProperties
      Removed value: -false
    • addedInput schema / properties / project
      Added value: +{
      +  "description": "Optional project/repo identifier this estimate belongs to, for cross-project analytics.",
      +  "minLength": 1,
      +  "type": "string"
      +}
    • addedInput schema / properties / session_id
      Added value: +{
      +  "description": "Optional session identifier (minted by a calling agent/hook) used to deduplicate repeated estimate calls for the same task within a session.",
      +  "minLength": 1,
      +  "type": "string"
      +}
    • addedInput schema / properties / task_label
      Added value: +{
      +  "description": "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.",
      +  "minLength": 1,
      +  "type": "string"
      +}
  2. First observedv0.1.0

TDQS

A4.5/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

The annotations already declare that the tool is read-only, idempotent, non-destructive, and closed-world, so safety behavior is covered. The description adds useful context about the estimation basis: model-specific calibration data, tokens per second, reasoning overhead, and tool-call latency. It does not describe output confidence or precision, but the core behavioral basis is disclosed.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is front-loaded with the core mapping and stays short. The sentence 'Bridges the gap between token-space... and time-space...' is somewhat conceptual rather than operational, keeping it from being maximally concise. Overall, it is clear and appropriately sized.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool has 8 parameters, no output schema, and full schema descriptions, so most parameter detail is already covered. The description supplies the return concept ('estimated wall-clock time') and the role of key inputs. It does not describe the exact output shape or precision of the estimate, but the definition is otherwise complete enough to call the tool correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3. The description adds meaning beyond isolated schema fields by naming the calibration factors that drive the estimate: token budgets, model-specific tokens per second, reasoning overhead, and tool-call latency. It does not add format or default details, but it helps an agent understand why the parameters matter.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource: 'Map LLM token budgets to estimated wall-clock time.' It also distinguishes itself from the sibling tool by saying to use token_cost_estimate when dollar cost matters. An agent can tell exactly what this tool does.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It provides an explicit alternative and condition: 'Use token_cost_estimate instead when dollar cost matters too.' This clearly tells the agent when not to use this tool and routes it to the right sibling. The purpose statement also implies the appropriate context: wall-clock time estimation rather than dollar cost.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.