Skip to main content
Glama
modelanalyzer-mcp

modelanalyzer-mcp

by yeaske

Estimate API cost

estimate_cost
Read-only

Calculate a model's per-request, daily, and monthly cost at list price using input/output tokens and requests per day.

Instructions

Cost per request, day and month for a model at list price, given tokens per request and requests per day.

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": {
      "model": "<model>",
      "inputTokens": "<inputTokens>",
      "outputTokens": "<outputTokens>"
    },
    "name": "estimate_cost"
  }
}

Input Schema

NameRequiredDescriptionDefault
modelYesModel id or name
inputTokensYesInput tokens per request
outputTokensYesOutput tokens per request
requestsPerDayNoRequests per day (default 1)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.2

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered. The description adds the meaningful caveat that figures are "at list price," i.e. not discounted or actual billed cost, but it says nothing about currency, pricing data vintage, or rounding, which matter for a cost estimate.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is a single tight sentence with zero padding, but it is a sentence fragment with no verb and buries the output granularity (per request, day, month) mid-phrase rather than front-loading it.

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?

For a read-only four-parameter estimator with full schema coverage, the description conveys the essentials: what is computed, the unit basis, and the list-price caveat. With no output schema, it should ideally state the return shape or currency, which is the main remaining gap.

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 description coverage is 100%, so all four parameters, including the requestsPerDay default of 1, are already documented in the schema. The description restates input tokens, output tokens, and requests per day without adding format, unit, or edge-case meaning beyond what the schema provides.

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 names the resource precisely: cost for a model, broken out per request, per day, and per month, computed from tokens per request and requests per day. It is a noun phrase rather than a verb+resource statement and does not differentiate itself from siblings like compare_models, but the computation is unambiguous.

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?

Mentioning "at list price" implies this is an estimation aid rather than actual billing, and the required inputs imply the scenario must be known in advance. There is no explicit guidance on when to use this versus compare_models or recommend_models, and no stated exclusions or prerequisites.

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