Skip to main content
Glama

BRAINIAC Cloud FinOps

Break down cloud spend

cloud-finops_spend-breakdown

Sum supplied charges by service, region, account, or a tag. When groupBy is omitted, charges are grouped by service. Currencies are not converted. Price $0.03 USDC. POST /api/v1/cloud-finops/spend-breakdown. 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_spend-breakdown"
  }
}

Input Schema

NameRequiredDescriptionDefault
csvNo
fileNo
rowsNo
tagKeyNo
groupByNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/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 discloses cost ($0.03 USDC), the payment gate ("Unpaid calls return 402 and do not run"), the transport (POST /api/v1/cloud-finops/spend-breakdown), and that currencies are not converted. It does not state the response shape or the 5000-row cap, so behavioral coverage is strong but not complete.

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 compact sentences, front-loaded with the core behavior and followed by pricing, endpoint, and error path — no filler. The telegraphic fragments border on choppy, but every sentence carries 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?

For a tool with a nested 12-field row schema, three alternative input modes, no output schema, and no annotations, the description omits the input-mode choice, the accepted row shape, and the return format. The payment and currency notes are valuable, but an agent still cannot confidently construct a call from this description plus the parameter schema.

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 5 top-level parameters including a deeply nested rows object, so the description must compensate and largely does not. It explains groupBy's default and that currency is not converted, but never distinguishes the mutually exclusive csv/file/rows input modes or explains tagKey, which is the single biggest ambiguity for a caller.

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?

Uses a specific verb and resource: "Sum supplied charges by service, region, account, or a tag," which tells an agent this aggregates supplied cost rows rather than parsing or forecasting them. It is not contrasted against siblings like billing-csv-parse or cost-allocation, and the phrase "or a tag" is slightly at odds with the groupBy enum (service/region/account), which muddies the dimensions available.

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?

Gives one concrete default rule: "When groupBy is omitted, charges are grouped by service," which is genuinely useful selection guidance. It offers no when-to-use versus the many sibling cost tools and no guidance on choosing among the three charge-input modes (csv, file, rows).

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