Skip to main content
Glama
Sign In
finops-framework-mcp

finops-framework-mcp

by aaronmsoto
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Hybrid

Get official maturity assessment

get_maturity_assessment
Read-onlyIdempotent

Retrieve the official FinOps Framework maturity assessment text for a capability at crawl, walk, or run level, or all three.

Instructions

The official FinOps Framework maturity assessment prose for a capability, verbatim, at one level (crawl|walk|run) or all three. This is the Foundation's published assessment text, not a parsed breakdown.

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": {
      "capability": "<capability>"
    },
    "name": "get_maturity_assessment"
  }
}

Input Schema

NameRequiredDescriptionDefault
levelNoOne level; omit for all three official levels
capabilityYesCapability slug, e.g. 'allocation'

Output Schema

NameRequiredDescriptionDefault
levelsYes
capabilityYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A4/5.0
Behavior4/5

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

Annotations already establish read-only, idempotent, closed-world behavior, so the safety profile is covered. The description adds genuinely useful context about the nature of the payload — verbatim official published text rather than a normalized/parsed representation — which shapes how an agent should present or trust the output.

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?

Two sentences, zero filler, with the most decision-relevant information (what it returns, its verbatim character, the level scoping) front-loaded.

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

Completeness4/5

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

An output schema exists, so return values need no explanation, and annotations cover the behavioral profile. The description is complete enough for a simple two-parameter read; only a direct pointer to the alternative assessment tool would improve it.

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 coverage is 100%: the enum values and the 'omit for all three' behavior are already documented in the input schema. The description repeats the level vocabulary but adds no slug syntax or format detail beyond what the schema provides, so the baseline 3 applies.

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?

Names a specific verb and resource ('get the official FinOps Framework maturity assessment prose for a capability') and pins the scope precisely (one level or all three). The clause 'not a parsed breakdown' separates it from derived-text siblings like get_maturity_model, so an agent can choose without opening schemas.

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 contrast with 'a parsed breakdown' implies when to prefer this tool over an interpretive one, but no sibling is named and there is no explicit when/when-not guidance relative to get_maturity_model or assess_maturity_path. Usage is inferable rather than stated.

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

Deploy Server

Other Tools