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

finops-framework-mcp

by aaronmsoto
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Hybrid

Maturity gap between two levels

assess_maturity_path
Read-onlyIdempotent

Retrieve official FinOps maturity assessment guidance for a capability across the levels between its current and target state, showing evidence to look for when maturing.

Instructions

For one capability, the official maturity assessment text at each level between current and target — evidence to look for when maturing. To get one level's assessment text on its own (or all three at once), use get_maturity_assessment instead.

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>",
      "current_level": "<current_level>",
      "target_level": "<target_level>"
    },
    "name": "assess_maturity_path"
  }
}

Input Schema

NameRequiredDescriptionDefault
capabilityYesCapability slug, e.g. 'allocation'
target_levelYesEnding maturity level, inclusive — must be above current_level
current_levelYesStarting maturity level, exclusive — the gap begins above this

Output Schema

NameRequiredDescriptionDefault
gapYes
capabilityYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A4.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and closed-world behavior, so the safety profile is covered. The description adds useful content semantics ('evidence to look for when maturing') but says nothing about ordering, empty-range handling, or size of the returned text; with annotations carrying the safety burden, this is adequate but not rich.

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 waste, with the primary behavior front-loaded and the sibling disambiguation placed second. Nothing redundant with the name or title.

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?

An output schema exists, so return values need not be explained; params are fully documented at 100% coverage; annotations cover the read-only/idempotent profile. Combined with the explicit sibling routing, an agent has everything needed to call this 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 100% and both level parameters are enums with inclusive/exclusive semantics already documented in the schema. The description reinforces the range concept ('between current and target') but adds no format or constraint detail beyond the schema, so the baseline of 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?

States a specific verb+resource: returns the official maturity assessment text at each level between a current and target level, for one capability. It also explicitly distinguishes itself from the sibling get_maturity_assessment, so an agent can route correctly without opening any 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?

Names the alternative (get_maturity_assessment) and the exact conditions that select it — one level alone, or all three at once — making this tool's niche (a contiguous range/gap) unambiguous.

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