estimate_cost

How much will this cost and how long will it take? Free and needs no account.

Scope: Discovery/session-dependent. Catalogue annotation: Read. Additional ownership and role checks may apply.

REST: POST /v1/estimates.

Arguments

Field

Type / accepted values

Required

Default

Constraints / meaning

operation

"geometry" / "mesh" / "simulation" / "prediction"

Yes

Omitted

cells

integer or null

No

null

minimum: 1000; maximum: 20000000; Mesh target cells (operation=mesh) or the simulation mesh’s cell count. Defaults to 1 million for meshes; for simulations supply cells or mesh_artifact_id.

mesh_artifact_id

string (uuid) or null

No

null

Owned mesh whose verified cell count to use (signed-in callers only).

simulation_type

"rans" / "urans" / "cht"

No

"rans"

architecture

"fluxcore" / "workhorse" / "krylov"

No

"fluxcore"

Use the live schema and the applicable workflow guide for semantics.

max_iterations

integer or null

No

null

minimum: 1; maximum: 1000000; Steady RANS/CHT iteration ceiling (default 6000).

n_physical_steps

integer or null

No

null

minimum: 1; maximum: 1000000

inner_iterations

integer or null

No

null

minimum: 1; maximum: 10000

mesh_max_attempts

integer

No

1

minimum: 1; maximum: 6; Total authorized full mesh attempts, for the upper time estimate. Use 1 for retry_policy=review; for automatic, copy max_remesh_iterations (octree/OpenFOAM) or max_target_iterations (structured). Read-only estimation does not authorize a retry. Automatic rebuilds are not charged: a mesh costs the same credits however many attempts it takes.

Calling the tool

Use tools/call with this tool’s exact name and an arguments object matching the fields above. Get the complete live schema before supplying advanced controls:

{
  "name": "get_tool_schema",
  "arguments": {
    "name": "estimate_cost",
    "include_definitions": false
  }
}

Result and continuation

Inspect isError and structuredContent. Keep returned job, operation and artifact IDs. A pending operation_id is followed with get_operation; a compute job is followed with get_job. A wait timeout does not cancel work. Follow returned polling intervals and retain the same idempotency key when reconciling the same submission.

See agent workflow, jobs and operations, uploads, results and error recovery for the applicable lifecycle. MCP annotations describe tool behaviour; they are not blanket permission to run paid work or change account state.