Skip to main content
Glama

BRAINIAC Cloud FinOps

Forecast monthly cloud cost

cloud-finops_monthly-cost-forecast

Fit a line through at least three supplied monthly totals, or multiply the average daily cost by the length of the next month when at least 14 days are supplied. Less history is not forecast. Price $0.05 USDC. POST /api/v1/cloud-finops/monthly-cost-forecast. Unpaid calls return 402 and do not run.

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": "cloud-finops_monthly-cost-forecast"
  }
}

Input Schema

NameRequiredDescriptionDefault
csvNo
fileNo
rowsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/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 a solid job: it discloses the two algorithmic paths and their data thresholds, the endpoint, that there is a $0.05 USDC charge, and that unpaid calls return 402 without running. It omits what the response contains (no output schema exists) and how mixed currencies or multi-service rows are aggregated, which are material for a forecasting tool.

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?

Four tight sentences: method logic first, then the exclusion, then price and transport details. No filler. The dense opening sentence packing two conditional methods is slightly hard to parse but every clause carries operational information.

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

Completeness3/5

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

For a paid, unannotated tool with a complex nested input and no output schema, the description covers method, cost, and failure mode but leaves the input contract and the shape of the returned forecast undocumented. It is adequate to know whether to attempt the call, less adequate to know how to construct one.

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% across three top-level inputs, one of which is a deeply nested row object with date/service/cost/currency fields. The description only obliquely references 'supplied monthly totals' and 'days,' never explaining the csv string, the file object, or the rows array, nor whether these are alternative input modes. Agents must reverse-engineer the entire input contract from the schema.

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 a specific operation (fit a line / extrapolate daily average to produce a monthly cost forecast) on a specific resource (monthly cloud spend), and the stated methods distinguish it from siblings like spend-breakdown or cost-anomaly-detect. It stops short of explicitly naming an alternative tool, so it is clear but not sibling-differentiating.

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

Usage Guidelines4/5

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

It gives concrete input thresholds that determine which method applies (three or more monthly totals vs. at least 14 daily datapoints) and an explicit exclusion: 'Less history is not forecast.' That is real when-to-use/when-not guidance. It does not point to an alternate tool for cases with insufficient history, which caps it below 5.

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.

Resources