Skip to main content
Glama

calculate_cloud_vs_local_breakeven

Compare cloud inference costs with buying and running a local board to find the breakeven point for a model and daily token volume.

Instructions

Compare cloud inference cost vs buying and running a local board.

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": {
      "daily_tokens": "<daily_tokens>",
      "model": "<model>"
    },
    "name": "calculate_cloud_vs_local_breakeven"
  }
}

Input Schema

NameRequiredDescriptionDefault
modelYes
daily_tokensYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

C2.6/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It doesn't disclose assumptions of the breakeven model, the time horizon, cost components, units, or whether results are estimates versus authoritative figures.

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?

A single tight sentence with the comparison front-loaded and no wasted wording. It is appropriately short but perhaps too terse given zero schema coverage.

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

Completeness1/5

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

Both parameters are required yet completely undocumented, and with an output schema present the description needn't explain returns. However, missing units, model format, and cost assumptions make correct invocation hard to guess.

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

Parameters2/5

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

Schema coverage is 0% and the description adds no meaning for either parameter. It does not define what 'model' should be (name, ID, or provider-specific string) or whether 'daily_tokens' is input, output, or combined tokens.

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?

States a specific comparison task: cloud inference cost versus buying and running a local board. Distinguishes it from siblings like get_best_inference_provider and get_board_history, though it doesn't name them explicitly.

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?

No guidance on when to use this versus alternatives, no prerequisites, and no exclusions. An agent must infer that this is a cost-modeling tool rather than a data lookup.

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