Skip to main content
Glama

cost_model

Read-onlyIdempotent

Calculates auditable cost scenarios from caller-supplied unit rates, quantities, and source URLs, so you can document pricing assumptions without guessing AWS prices.

Instructions

Calculate an auditable scenario using caller-supplied unit rates and source URLs. Does not guess AWS prices or credit coverage.

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": {
      "items": "<items>"
    },
    "name": "cost_model"
  }
}

Input Schema

NameRequiredDescriptionDefault
itemsYes
currencyNoUSD
contingencyPercentNo

Output Schema

NameRequiredDescriptionDefault
kindNo
itemsNo
sourcesNo
currencyNo
excludedNo
subtotalNo
validatedNo
limitationNo
creditWarningNo
contingencyPercentNo
totalWithContingencyNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv0.5.0
    • removedInput schema / properties / items / items / additionalProperties
      Removed value: -false
    • changedInput schema / required
      Previous value: -[
      -  "currency",
      -  "items",
      -  "contingencyPercent"
      -]New value: +[
      +  "items"
      +]
    • addedOutput schema / properties / limitation
      Added value: +{
      +  "type": [
      +    "string",
      +    "null"
      +  ]
      +}
    • addedOutput schema / properties / sources
      Added value: +{
      +  "type": "array"
      +}
    • addedOutput schema / properties / validated
      Added value: +{
      +  "type": [
      +    "boolean",
      +    "null"
      +  ]
      +}
  2. First observedv0.4.1

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so the safety profile is covered. The description adds one genuinely new trait — it performs no external price lookup and relies entirely on caller input. It omits how the computation behaves (whether contingency applies per item or to the total, whether any currency conversion occurs), which matters for a calculation tool.

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

Conciseness5/5

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

Two sentences, zero filler, with the positive scope stated first and the constraint second. Every clause earns its place.

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

Completeness2/5

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

An output schema and annotations relieve part of the burden, but this tool requires a nested array of up to 50 items with six required fields each, and the description never explains the item model or the unit/price relationship needed to compute correctly. For a calculation tool where wrong unit assumptions silently produce wrong numbers, this is a material gap.

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 description coverage is 0%, so the description carries the full burden, and it only loosely maps to two of the inputs ('unit rates' for pricePerUnit, 'source URLs' for source). It says nothing about quantity, unit granularity (per-hour vs per-month matters enormously), priceDate, currency (USD/BRL), or contingencyPercent's default of 20.

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 verb and resource ('calculate an auditable scenario') and pins down the input contract at a high level — caller-supplied unit rates and source URLs. The negative clause ('does not guess AWS prices or credit coverage') separates it from pricing/lookup siblings like aws_knowledge_read or finops_unit_economics, though it never names them.

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?

The exclusion ('does not guess AWS prices') implies the caller must first gather rates elsewhere before invoking this tool, which is useful implied routing. However, there is no explicit 'use this when X, use finops_unit_economics when Y' guidance, and nothing about prerequisites or validity requirements for the supplied rates.

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