Find the right FinOps guide
find_referencesIdentify relevant FinOps guidance by asking a cloud or AI spend question, or filter by domain, capability, phase, persona, and maturity to get ranked references and sections.
Instructions
Find which guidance serves a FinOps question - how to commit, size, allocate, charge back, forecast, or govern cloud and AI spend.
Use this with ``query`` for a question in the user's own words rather
than in FinOps Framework terms: "how should we size our first Savings
Plan when usage is seasonal", "we hold SQL Server licences with Software
Assurance, BYOL or licence-included?", "our forecast missed by 20%",
"who should own commitment purchases", "combien s'engager en Savings
Plans". Every guide declares the questions it answers (English and
French); the result is ranked by those, then by title and section
headings, and each entry carries ``matched_question`` and
``suggested_section``, the heading that ``get_reference(name=,
section=)`` takes. The facets narrow the set first; ``query`` ranks what
is left.
Use this with the facets alone for a question already in FinOps
Framework terms (domain, capability, phase, persona, maturity): "what
does a Crawl-stage org tackle first", "the Engineering reading list",
"what should Finance own in chargeback".
All filters are optional and combine with AND semantics. Facet matching
is case-insensitive and exact (not substring). Examples:
- ``find_references(query="our forecast missed by 20%, was it the model or the drivers")``
- ``find_references(domain="Optimize Usage & Cost")``
- ``find_references(phase="Optimize", persona="Engineering")``
- ``find_references(persona="Engineering", persona_primary_only=True)``
- ``find_references(capability="Rate Optimization")``
- ``find_references(maturity="Crawl")``
Args:
query: the user's question or symptom in their own words, up to
1,000 characters, English or French. Ranks the facet-filtered guides by
the questions they declare, their title and their headings;
returns at most five, best first, each with ``match_score``,
``matched_question`` and ``suggested_section``.
domain: FinOps Framework domain (e.g. ``"Optimize Usage & Cost"``,
``"Quantify Business Value"``, ``"Manage the FinOps Practice"``).
capability: FinOps capability (matches ``fcp_capability`` and
``fcp_capabilities_secondary``).
phase: FinOps phase (``"Inform"``, ``"Optimize"``, ``"Operate"``).
persona: Persona (matches ``fcp_personas_primary`` and
``fcp_personas_collaborating``).
maturity: Entry maturity level (``"Crawl"``, ``"Walk"``, ``"Run"``).
persona_primary_only: when True, ``persona`` matches only the primary
list. Useful when the default match barely narrows the set -
broad personas like Engineering collaborate on nearly every file,
so filtering on collaboration is descriptive, not discriminating.
``persona="Engineering", persona_primary_only=True`` is the
engineering reading list; the default is the everything-they-touch
view.
Returns ``{"filters": {...}, "references": [...], "total": N}``. With
``query`` the entries are ranked and capped at five. A facet filter that
matches nothing also returns `hint` and `valid_values`, so a typo is
distinguishable from a genuine gap in coverage; a ``query`` that matches
nothing returns `hint` alone.
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": "find_references"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| phase | No | ||
| query | No | ||
| domain | No | ||
| persona | No | ||
| maturity | No | ||
| capability | No | ||
| persona_primary_only | No |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||