Skip to main content
Glama

BRAINIAC Cloud FinOps

Parse a billing CSV

cloud-finops_billing-csv-parse

Read brainiac-billing-v1 CSV or JSON charges. Required columns are date, service, cost, and currency. Native cloud-provider exports are rejected. Price $0.03 USDC. POST /api/v1/cloud-finops/billing-csv-parse. 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_billing-csv-parse"
  }
}

Input Schema

NameRequiredDescriptionDefault
csvNo
fileNo
rowsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose real behavior: cost of $0.03 USDC, the HTTP endpoint, that unpaid calls return 402 and do not execute, and that foreign export formats are refused. It never states whether parsing persists anything or is a pure transformation, nor what a successful response looks like despite there being no output schema to fall back on.

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?

Four short sentences, zero padding, and the load-bearing constraint (format identity, then required columns, then rejection rule) comes before the operational details of price and endpoint. The HTTP route is the weakest sentence but still gives an agent a concrete handle on the call.

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 tool with nested objects, three alternative input modes, no annotations and no output schema, the description covers commercial and rejection behavior well but leaves the two highest-risk gaps open: which input parameter to supply and what the parse actually returns. An agent can probably call it correctly but cannot predict the result.

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 only partially does. It names the four required row fields (date, service, cost, currency), but the schema's three top-level parameters appear to be alternative input modes (inline csv string, base64 file object, rows array) and the description gives no guidance on mutual exclusivity or precedence. Size limits on csv (200k chars) and file (12MB base64) are also undisclosed.

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

Purpose5/5

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

States a specific verb and resource ('Read brainiac-billing-v1 CSV or JSON charges') and pins down scope with two hard constraints: required columns (date, service, cost, currency) and rejection of native cloud-provider exports. That rejection rule alone lets an agent distinguish this ingestion tool from the analytics siblings like spend-breakdown or cost-allocation.

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?

Provides a concrete when-not condition ('Native cloud-provider exports are rejected'), which is exactly the kind of disqualifier an agent needs before submitting a file. It stops short of naming an alternative route for rejected inputs or explaining which of the three input modes to choose, so it is clear context without full routing.

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