Cloud FinOps Skill & MCP

Browse the FinOps knowledge library

list_references

Read-onlyIdempotent

See what FinOps guidance is available: billing mechanics, commitment strategy, allocation and chargeback, AI cost management, and per-provider cost handbooks (AWS, Azure, GCP, OCI, Databricks, Snowflake, ...).

Use this to discover what the library covers. When the question already
names a FinOps domain, phase, persona or maturity, ``find_references``
returns only the matching references.

Returns a dict shaped ``{"references": [...], "total": N}`` where each
entry includes ``name``, ``title``, a one-line ``description``, the
discriminating FCP facets (``fcp_domain``, ``fcp_capability``,
``fcp_phases``, ``fcp_personas_primary``, ``fcp_maturity_entry``) and
``approx_tokens``.

``approx_tokens`` gives each file's size before it is fetched: the library
runs from about 2,000 to about 15,000 tokens per file, and
``get_reference(name, section=...)`` returns one section of a large one.

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedAug 19, 2026

TDQS

A4.6/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and a closed-world scope, so the safety profile is covered. The description adds genuinely new behavioral context: approximate per-file size (2,000-15,000 tokens) and the fact that get_reference(name, section=...) fetches just one section of a large file, which is real cost-planning information. It is slightly redundant in spelling out the return shape given an output schema exists.

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?

Three short paragraphs, front-loaded with purpose, then routing, then return shape and cost guidance — well ordered and easy to scan. The detailed field enumeration overlaps with the output schema and could be trimmed without loss.

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?

For a zero-parameter, read-only browse tool this covers everything an agent needs: what is listed, when to prefer find_references, what comes back, and how big the payloads are before fetching. Nothing material is missing.

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

Parameters4/5

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

The tool takes zero parameters, so the baseline is 4 and nothing needs compensating for. The description instead documents the shape of the returned entries (name, title, description, fcp_* facets, approx_tokens), which helps an agent interpret results even though it is not strictly parameter semantics.

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?

The description opens with a specific verb-plus-resource ('See what FinOps guidance is available') and enumerates the actual coverage areas (billing mechanics, commitment strategy, allocation/chargeback, AI cost, per-provider handbooks). It also names the sibling it is NOT (find_references), so an agent can distinguish the two without opening a schema.

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?

Explicit when-to-use: 'Use this to discover what the library covers.' Explicit alternative and its selection condition: when the question already names a domain, phase, persona or maturity, find_references returns only matches. This is a clean routing rule with no inference required.

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.