Skip to main content
Glama

BRAINIAC Cloud FinOps

Report cloud cost evidence

cloud-finops_cost-optimization-report

Combine the supplied billing, usage, price, and budget checks. Recommendations repeat the evidence and the assumption. No account is connected and no resource is changed. Price $0.12 USDC. POST /api/v1/cloud-finops/cost-optimization-report. 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_cost-optimization-report"
  }
}

Input Schema

NameRequiredDescriptionDefault
csvNo
fileNo
rowsNo
budgetNo
tagKeyNo
groupByNo
optionsNo
volumesNo
resourcesNo
minimumDaysNo
cpuThresholdNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full burden and does well: it declares no account is connected and no resource is changed (a no-side-effect, no-credential guarantee), states the exact price ($0.12 USDC), the transport (POST /api/v1/cloud-finops/cost-optimization-report), and the failure semantics (unpaid calls return 402 and do not run). What remains undisclosed is the shape of the returned report and any validation behavior when the supplied datasets are inconsistent.

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?

Five short sentences, zero filler, with the core behavior and the safety/payment constraints front-loaded. The explicit HTTP path is arguably redundant detail for an agent, but every other sentence carries decision-relevant information.

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?

This is a high-complexity tool: 11 top-level parameters, nested item objects, an enum, and no output schema. Given that the schema documents nothing, the description should explain which inputs are required for which analysis and what the report contains; instead it only states that recommendations repeat their evidence and assumption, leaving an agent unable to assemble a valid call confidently.

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 11 parameters with deep nested objects, so the description must compensate and largely does not. It gestures at four input families (billing, usage, price, budget) but never maps them to parameters such as rows/csv/file, resources, volumes, options, budget, groupBy, tagKey, minimumDays, or cpuThreshold, and gives no defaults, formats, or interaction rules (e.g. csv vs file vs rows precedence, or how minimumDays and cpuThreshold gate the analysis).

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

"Combine the supplied billing, usage, price, and budget checks" plus "Recommendations repeat the evidence and the assumption" conveys that the tool ingests FinOps inputs and emits an evidence-backed optimization report, but the verb is generic and the output artifact is never named outright. It also fails to distinguish itself from close siblings such as cloud-finops_idle-resource-detect, cloud-finops_unused-storage-detect, and cloud-finops_budget-variance-analyze, all of which appear to consume similar inputs.

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

Usage Guidelines2/5

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

There is no when-to-use guidance, no prerequisites, and no named alternative. An agent cannot tell from this text whether to call this tool rather than the idle-resource or budget-variance siblings, or whether this tool is a superset that should be preferred.

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