Cloud FinOps Skill & MCP

Current figures from an OptimToken guide

get_live_figures

Read-onlyIdempotent

Get the current value of a figure a reference quotes with a date.

Use this when a reference quotes a figure from an OptimToken guide
("measured on the 2026-10-25 OptimToken catalogue") and the answer needs
the current value: the Compute Savings Plan or reservation discount, the
gap between a flexible and a locked commitment, the ARM discount against
Intel and AMD, the share of LLM models with a batch rate. It fetches the
guide's figures file, rebuilt daily, and returns it as published.

Args:
    guide: The guide slug, lowercase letters, digits and hyphens. Guides
        with figures today: ``"savings-plans-vs-reserved-instances"``,
        ``"arm-against-x86"``, ``"batch-api-economics"``.

Returns ``{"document": {...}, "fetched_at": ..., "source": "live" |
"cached", "note": ...}``, plus ``cache_age_seconds`` when cached (six-hour
cache). ``document`` is the file unchanged: ``guide``, ``title``,
``url``, ``dataSource``, ``snapshotDate`` (the catalogue the figures come
from), ``dateModified`` and ``figures``, where discounts are fractions
(0.2743 is 27.4%) and each key names a median, a range or a count.

An unknown slug returns ``{"error", "available_guides", "suggestions"}``.
Any other failure (timeout, HTTP error, invalid JSON) returns
``{"error", "fallback"}``: the dated figure in the reference then stands,
quoted with its date.

Input Schema

Name	Required	Description	Default
`guide`	Yes

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 25, 2026

TDQS

A4.9/5.0

Behavior5/5

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

Annotations only say read-only, idempotent and open-world; the description adds the daily rebuild cadence, the six-hour cache and the resulting 'source'/'cache_age_seconds' fields, plus both failure shapes (unknown slug with suggestions, other errors with fallback). That is real behavior an agent cannot get from the annotations.

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?

Front-loaded with the purpose and use case, then Args/Returns/errors in a clean order. Slightly long — the parenthetical catalogue example is repeated and the figure-category list could be tighter — but every section adds information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Covers the one parameter, the return document's fields and units (discounts as fractions, keys naming medians/ranges/counts), snapshot dating, cache semantics, and both error branches. Nothing needed to call it or interpret the result is missing, even though an output schema exists.

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

Parameters5/5

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

Schema coverage is 0% and the schema only declares a bare string, so the description carries the full burden: it specifies the slug format (lowercase letters, digits, hyphens), lists the currently valid slugs, and documents the error payload returned for an unknown slug.

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 ('Get the current value of a figure a reference quotes with a date') and makes the live-vs-dated distinction explicit, which separates it from the sibling reference and playbook lookup tools.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives a concrete trigger condition (a reference quotes a figure like 'measured on the 2026-10-25 OptimToken catalogue' and the answer needs the current value), enumerates the kinds of figures covered, and states what to do when the call fails (keep the dated figure with its date).

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Cloud FinOps Skill & MCP tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.