Skip to main content
Glama

token_time_bridge

Read-onlyIdempotent

Map LLM token budgets to estimated wall-clock time using model-specific calibration. Plan agentic tasks by factoring 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).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tokensYesTotal number of tokens in the LLM request (prompt + completion).
modelYesLLM model identifier. Unknown models fall back to generic estimates.
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
task_typeNoOptional task type for feedback matching.
Behavior4/5

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

The description adds significant behavioral context beyond the annotations, explaining that it uses model-specific calibration data and accounts for reasoning depth, tool-call latency, and token count. This helps the agent understand the estimation process, though it does not mention limitations or accuracy bounds.

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

Conciseness5/5

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

The description is three sentences, each adding value: core purpose, mechanism, and motivation. It is front-loaded and contains no redundant or filler content.

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

Completeness3/5

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

The tool has no output schema, but the description does not mention the return format (e.g., seconds, minutes). It also omits the role of the optional 'task_type' parameter. While the input behavior is well-covered, the lack of output description is a gap.

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

Parameters3/5

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

Schema coverage is 100% with descriptions for all parameters, so the baseline is 3. The description does not elaborate on each parameter beyond what the schema already provides, but the overall context of how parameters contribute to the estimation is helpful.

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

Purpose4/5

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

The description clearly states the tool maps token budgets to wall-clock time using calibration data. It uses a specific verb ('Map') and identifies the resource ('LLM token budgets'). However, it does not explicitly differentiate from siblings like calibrate_estimates or token_cost_estimate, though the purpose is specific.

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternatives, no exclusions, and no context about prerequisites or typical use cases. It simply states what it does without any when-to-use or when-not-to-use information.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/KyaniteLabs/Epoch'

If you have feedback or need assistance with the MCP directory API, please join our Discord server