Skip to main content
Glama
c3-yang-song

infra-advisor-mcp

by c3-yang-song

estimate_inference_cost

Compare cloud API and self-hosted inference costs for any token volume, with break-even analysis and options for quantization and latency targets.

Instructions

Compare cloud API and self-hosted inference costs for a given token volume.

Returns monthly cost for all major API providers and self-hosted options, with break-even analysis. Self-hosted sizing accounts for two levers:

  • quantization (fp8/int8/int4) shrinks model VRAM (so fewer GPUs per replica) and lifts throughput, at a small quality cost.

  • the latency target sizes how many replicas are needed to serve the daily output volume at peak load — so an option is only "cheaper" if it can actually keep up. Each self-hosted option reports per-replica topology, replicas_needed, and total GPUs.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
daily_input_tokensYesAverage input tokens per day.
daily_output_tokensYesAverage output tokens per day.
daily_imagesNoNumber of images processed per day (for vision/multimodal workloads). When non-zero, image costs are added to the monthly bill for vision-capable models.
use_caseNogeneral
qualityNohigh
latencyNoTarget responsiveness (realtime/near_realtime/batch/offline) — drives replica sizing.near_realtime
quantizationNoSelf-hosted serving precision (none/fp8/int8/int4).none

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
daily_input_tokensYes
daily_output_tokensYes
daily_imagesYes
monthly_input_tokensYes
monthly_output_tokensYes
quantizationYes
required_throughput_tpsYes
api_optionsYes
self_hosted_optionsYes
cheapest_apiYes
cheapest_self_hostedYes
recommendationYes
Behavior4/5

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

No annotations provided, so description takes full burden. It details self-hosted sizing logic involving quantization and latency, and what returns are provided (break-even, topology, replicas). No contradictions.

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?

Description is a single paragraph with front-loaded purpose. It is informative but could be more structured (e.g., bullet points). No wasted sentences.

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?

Given tool complexity and existence of an output schema (not shown), description adequately explains return values and key levers. It covers self-hosted sizing and break-even analysis sufficiently.

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

Parameters4/5

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

Schema coverage is 71%; description adds meaningful context for quantization and latency (e.g., 'shrinks model VRAM' and 'latency target sizes replicas'), but does not elaborate on required parameters beyond schema.

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?

Description clearly states it compares cloud API and self-hosted inference costs for a given token volume, and distinguishes from siblings like estimate_training_cost or estimate_maintenance_cost by focusing on inference cost estimation specifically.

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

Usage Guidelines3/5

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

Usage is implied but not explicitly guided: no statements on when to use vs alternatives like compare_cloud_vs_onprem. The description focuses on what it does, not when to invoke it.

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/c3-yang-song/LLM-Infra-Advisor-MCP'

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