Skip to main content
Glama

BRAINIAC Cloud FinOps

Allocate cloud cost by tag

cloud-finops_cost-allocation

Group supplied charges by one tag key. Charges without that tag remain unallocated. Price $0.04 USDC. POST /api/v1/cloud-finops/cost-allocation. 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": {
      "tagKey": "<tagKey>"
    },
    "name": "cloud-finops_cost-allocation"
  }
}

Input Schema

NameRequiredDescriptionDefault
csvNo
fileNo
rowsNo
tagKeyYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior4/5

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

With no annotations, the description carries real behavioral weight: it discloses the price ($0.04 USDC), the payment gate (HTTP 402 blocks execution), and how untagged charges are handled (left unallocated rather than dropped). It omits output shape and whether csv/file/rows inputs are mutually exclusive, but the commercial and failure-mode disclosures are unusually good for a no-annotation tool.

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, each load-bearing: purpose first, edge-case semantics second, cost and endpoint next, failure mode last. No filler and nothing buried.

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 4-parameter tool with nested objects, no output schema, and no annotations, the description covers cost, failure gating, and unallocated handling well, but leaves the input-source contract and the response content unexplained. Adequate to attempt a call, not complete enough to call confidently without inspecting the 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%, so the description must compensate, and it explains only that tagKey is a single tag key. The other three parameters (csv, file, rows) — the actual input-source choice with a nested file object and a 5000-row item schema — are never mentioned, leaving an agent to guess whether these are alternatives or combined.

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?

"Group supplied charges by one tag key" names a specific verb (group) and resource (charges) and scopes it to a single tag key, which implicitly separates it from broader breakdown/compare siblings. It stops short of naming any sibling or stating how results differ from spend-breakdown, so it is clear but not fully differentiated.

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?

Usage is only implied: an agent can infer this is the tool for tag-based allocation, but there is no statement of when to prefer it over cloud-finops_spend-breakdown or compute-cost-compare, and no prerequisites or exclusions. The 'unallocated' sentence hints at the expected scenario but is framed as behavior, not guidance.

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