Skip to main content
Glama

Server Details

Gemini 4 agent-run cost simulator over MCP: true per-turn totals vs naive estimates.

Ownership verified
Status
Healthy
Uptime
100.0% over the last 24 hours
Last Tested
Transport
Streamable HTTP · MCP 2025-06-18
URL
Repository
gowinder/geminicost-mcp
GitHub Stars
0
Server Listing
Gemini Cost Simulator
ChatGPT
–
Claude
–

TDQS

A3.8/5.0

Scored across 2 tools

Disambiguation5/5

The two tools have clearly distinct purposes: estimate_agent_run simulates a multi-turn agent run, while get_gemini_pricing retrieves the pricing segment and rates for a date/model. An agent can easily tell which tool to use for cost simulation versus pricing lookup.

Naming Consistency5/5

Both names use consistent snake_case with a clear verb-led pattern: estimate_agent_run and get_gemini_pricing. The convention is predictable and readable.

Tool Count4/5

Two tools is small, but for a narrowly scoped Gemini cost simulator it is reasonable: one tool retrieves pricing data and one tool uses it to simulate run cost. It is slightly thin but not inappropriate for the domain.

Completeness4/5

The surface covers the core lifecycle: looking up pricing segments and estimating turn-by-turn agent run costs, including pre- and post-price-change scenarios. Minor gaps exist around batch comparisons or broader model exploration, but the advertised purpose is well covered.

Available Tools

2 tools
estimate_agent_runEstimate the cost of one Gemini 4 agent runBInspect

Turn-by-turn cost of a Gemini 4 agent run: every turn re-sends the growing context as input, thinking tokens are billed at the output rate. Returns the rates in force on the chosen date, the simulated total, the naive first-turn × turns estimate and their multiplier. Before the 2026-12-01 price change it also returns afterIncrease: the same run priced at the announced 2026-12-01 rates.

Inputs: turns (required), modelId (required), thinkingLevel (required), outputTokensPerTurn (required), +4 more.

get_gemini_pricingGet Gemini 4 list prices for a dateAInspect

Price segment in force on a date for every recorded Gemini 4 model, or for one model: input and output USD per 1,000,000 tokens, the segment start and end dates and its status. Segments marked announced-unpriced have no published values and are reported as such.

Inputs: date, modelId.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    Related MCP Connectors

    Related MCP Servers

    Try in Browser

    Glama MCP Gateway

    Add one secure layer between your agents and this server.