Skip to main content
Glama

estimate

Read-only

Predict how long a render or batch will take on this PC and check queue length without starting work.

Instructions

How long a render (same settings as render) or a whole batch (items = a list of render settings) would take on this PC, and how long the queue is, WITHOUT starting anything.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "estimate"
  }
}

Input Schema

NameRequiredDescriptionDefault
imageNo
itemsNo
modelNo
speedNo
styleNo
widthNo
cameraNo
heightNo
promptNo
qualityNo
secondsNo
movementNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint=true, destructiveHint=false, closed-world), so the bar is lower; the description still adds real value by stating nothing is started, that timing is specific to 'this PC', and that queue depth is reported alongside duration. It does not say whether the estimate is accurate/approximate or how queue length affects the projection.

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?

A single sentence that front-loads the primary question (how long) and then qualifies it (batch mode, queue length, no side effects). No filler, and the most decision-relevant constraint ('WITHOUT starting anything') closes the sentence with emphasis.

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?

For a 12-parameter estimator with no output schema, the description covers what is measured but not what comes back — units, per-item vs. aggregate results, or whether an error/unknown is returned for an invalid batch. It is adequate to decide whether to call the tool, but thin for interpreting the result.

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?

With 12 parameters at 0% schema description coverage, the description carries the burden, and it only explains one: 'items = a list of render settings'. The pointer 'same settings as render' usefully implies the other ten parameters mirror that tool's schema, but no parameter's format, units, or defaults are clarified in the description itself.

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 uses a specific verb-and-object framing ('How long a render ... or a whole batch ... would take on this PC') and names the second output, queue length. It explicitly distinguishes itself from the write path via 'same settings as render' and 'WITHOUT starting anything', so an agent can separate it from the render/queue siblings without opening a schema.

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

Usage Guidelines4/5

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

The phrase 'WITHOUT starting anything' plus the reference to render establishes the clear context of a dry-run/pre-flight check, and the batch mode ('items = a list of render settings') signals the multi-job case. It stops short of an explicit 'use this before calling render' statement or any when-not-to guidance, so it is clear context rather than full routing.

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