Skip to main content
Glama

estimate_job_cost

Calculates exact upload/download network bandwidth (MB), task count, GFLOPs, and satoshi cost estimates for a distributed matrix multiplication C (m x n) = A (m x k) x B (k x n).

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": {
      "m": "<m>",
      "k": "<k>",
      "n": "<n>"
    },
    "name": "estimate_job_cost"
  }
}

Input Schema

NameRequiredDescriptionDefault
kYesInner dimension K (columns of A / rows of B).
mYesRows of matrix A (M > 0).
nYesColumns of matrix B (N > 0).
dtypeNoPrecision format ('fp32', 'fp16', 'bf16').fp32
grid_colsNoColumn partitions P_c when using output_grid_2d.
grid_rowsNoRow partitions P_r when using output_grid_2d.
tile_sizeNoTile block size dimension.
num_stripsNoStrip count when using outer_product_1d.
sats_per_gflopNoOverride worker price in satoshis per GFLOP.
partitioning_strategyNoMatrix partitioning strategy.output_grid_2d

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It does convey that the tool produces estimates (implying a non-mutating, side-effect-free computation) and that costs come from worker pricing that can be overridden, but it never states explicitly that nothing is executed, whether pricing is fetched live, or how accurate 'exact' is.

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 front-loaded sentence that packs the verb, the computation, and all four returned quantities with no filler. Nothing could be removed without losing information.

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?

With 10 parameters and no annotations or output schema, the description compensates by enumerating the four result categories, which effectively substitutes for an output schema. What remains missing is guidance on the interaction between the three partitioning strategies and the optional grid/strip parameters, but the core is covered.

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%, so every parameter including dtype, tile_size, num_strips, partitioning_strategy, and sats_per_gflop is already documented in the schema. The description adds only the m/k/n role mapping via the formula notation; it says nothing about how partitioning strategy choices affect the estimates. Baseline 3 applies.

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 uses a specific verb ('Calculates') and names the exact resource and outputs: upload/download bandwidth in MB, task count, GFLOPs, and satoshi cost for a distributed matmul C(m x n) = A(m x k) x B(k x n). An agent can distinguish this from execute_distributed_matmul by the 'estimate' framing, though the description never explicitly contrasts the two.

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?

There is no explicit when-to-use or when-not-to-use guidance, no mention of calling this as a pre-flight step before execute_distributed_matmul, and no stated prerequisites (e.g., needing network pricing data). The pre-execution estimation role is only inferable from the tool name and the word 'estimates'.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.