Skip to main content
Glama

Get Gemini 4 list prices for a date

get_gemini_pricing

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.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_gemini_pricing"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateNoISO date (YYYY-MM-DD) that selects the price segment in force that day. Defaults to today (UTC).
modelIdNoRestrict the answer to one model. Omit for all recorded models.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it enumerates what comes back (input/output USD per million tokens, segment start/end dates, status) and discloses the edge case that announced-unpriced segments have no published values. Read-only nature is implicit in 'price segment ... for every recorded model' but never contradicted.

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?

Two sentences, front-loaded with the core resource and scope, then the output and the unpriced-segment caveat. Dense but every clause carries information; the colon-delimited output list is efficient rather than padded.

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 no output schema and no annotations, the description compensates by describing the returned fields and the special announced-unpriced case, which is exactly what an agent needs to interpret results. It omits nothing critical for a two-parameter, zero-required read tool, though naming the sibling relationship would complete it.

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 both parameters are already documented in detail, including the ISO pattern and default-to-today behavior. The description reinforces that 'date' selects the segment in force and 'modelId' restricts to one model, but adds no syntax or format detail beyond the schema — 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?

States a concrete resource (Gemini 4 list prices) and scope (all recorded models or a single model) with the unit of measure (USD per 1,000,000 tokens). An agent can tell this is a raw price lookup rather than a cost computation like the sibling estimate_agent_run, though the sibling is not named explicitly.

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 by the phrasing 'price segment in force on a date' and the optional modelId restriction, but there is no explicit when-to-use versus estimate_agent_run guidance or any stated exclusion. The agent must infer that this returns list prices rather than an estimated run cost.

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.