Skip to main content
Glama

BRAINIAC Cloud FinOps

Analyze budget variance

cloud-finops_budget-variance-analyze

Subtract the supplied budget from the supplied charges inside the period. Missing days stay uncovered and are not filled with zero from another currency. Price $0.03 USDC. POST /api/v1/cloud-finops/budget-variance-analyze. Unpaid calls return 402 and do not run.

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": {
      "budget": "<budget>"
    },
    "name": "cloud-finops_budget-variance-analyze"
  }
}

Input Schema

NameRequiredDescriptionDefault
csvNo
fileNo
rowsNo
budgetYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.1/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 behavioral burden well: it discloses the endpoint, a per-call price of $0.03 USDC, that unpaid calls return 402 and do not run, and how missing days are handled with respect to currency. It stops short of describing the return shape or confirming read-only behavior, but the disclosed pricing and error semantics are valuable context an agent would not otherwise have.

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?

The core operation is front-loaded in the first sentence, with behavioral and billing details following. The fragmented 'Missing days' sentence is awkwardly worded, but the overall definition is compact and free of filler.

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 complex tool with nested objects, four parameters, 0% schema coverage, and no output schema, yet the description never explains the input formats (csv vs file vs rows) or what the variance result contains. The operational details it does give are useful, but significant gaps remain for a tool of this complexity.

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 must compensate, and it largely does not. It mentions only 'supplied budget' and 'supplied charges,' leaving the relationship between csv, file, and rows, and the structure of the budget object (amount, currency, periodStart, periodEnd), unexplained beyond 'inside the period.'

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 uses a specific verb and resource: it subtracts the supplied budget from the supplied charges inside the period, which is a concrete variance calculation. It is clear what the tool does, but it does not distinguish itself from siblings like spend-breakdown or cost-allocation, so an agent must infer why this tool over those.

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 explicit when-to-use guidance, no prerequisites, and no naming of alternatives. An agent can infer its purpose from the operation, but nothing tells it when to choose this tool over cost-allocation or spend-breakdown.

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