Skip to main content
Glama

BRAINIAC Cloud FinOps

Compare supplied compute prices

cloud-finops_compute-cost-compare

Multiply each supplied hourly price by the supplied hours. Options in different currencies are not converted, and no provider list price is added. Price $0.03 USDC. POST /api/v1/cloud-finops/compute-cost-compare. 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": {
      "options": "<options>"
    },
    "name": "cloud-finops_compute-cost-compare"
  }
}

Input Schema

NameRequiredDescriptionDefault
optionsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/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 load and does well: it discloses the pricing model ($0.03 USDC), the payment failure mode (402, call does not run), the transport (POST endpoint), and two important behavioral limits (no FX conversion, no list-price enrichment). It omits output behavior such as rounding, ordering, or whether a combined total is returned.

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, front-loaded with the computation and its two main caveats; operational details (price, endpoint, 402) follow in a sensible order. No filler, though the endpoint string is arguably the least agent-relevant element.

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 small arithmetic tool with one parameter and no output schema, the definition covers the core computation, currency semantics, and payment gating. What is missing is the shape of the result (per-option values plus a total? mixed-currency handling in the response?), which an agent needs to interpret the return value correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% and the only parameter is a nested array, so the description must compensate. It usefully explains that hourlyPrice and hours are multiplied and that currency is carried through unconverted, but it never mentions the 'name' field, the 2-8 option bounds, or the currency format constraints encoded in the schema.

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?

Opens with a precise verb and operation: multiply each supplied hourly price by supplied hours. The clause 'no provider list price is added' signals this is a pure calculator rather than a price-lookup tool, which separates it from provider-data siblings. It stops short of naming an explicit alternative.

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?

The negative guidance ('not converted', 'no provider list price') implicitly tells an agent when this tool is inappropriate, i.e. when it needs real list prices or a single-currency total. There is no positive statement of the situation that should select this tool over the sibling cost tools, so usage is only implied.

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