finops-framework-mcp

Overview Schema Source Related Servers Discussions Admin

Data changelog

get_changelog

Read-onlyIdempotent

Retrieve crawl-to-crawl differences in this server's finops.org content across up to 20 retained refreshes to see what changed between data versions.

Instructions

What changed between data versions of this server's crawled artifact (rolling window of the 20 most recent refreshes — the crawler caps the log at 20, so this tool covers the full retained history; the same data is at finops://framework/meta/changelog). Reflects crawl-to-crawl differences in finops.org content, not a Foundation-published changelog.

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": "get_changelog"
  }
}

Input Schema

Name	Required	Description	Default
`limit`	No

Output Schema

Name	Required	Description	Default
`entries`	Yes
`current_version`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.0Oct 20, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-open-world), but the description adds real behavioral context: the crawler caps the log at 20 refreshes, so the tool covers the full retained history rather than a truncated slice. That retention/cap behavior is exactly the kind of trait annotations cannot express, though it says nothing about ordering or response shape.

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?

Two front-loaded sentences that lead with the core purpose before qualifying scope and the mirroring resource URI. The long parenthetical is information-dense rather than wasteful, though it slightly buries the retention fact.

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?

With an output schema present, return-value explanation is unnecessary, and the description covers purpose, retention window, scope caveat, and alternate access path. The one gap is that the only input parameter is undocumented in both the schema and the description.

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?

The single `limit` parameter has 0% schema description coverage and is never named in the description, so its role (number of entries returned) and default of 5 are left implicit. The description does partially compensate by explaining the 20-entry cap, which gives the schema's maximum=20 meaning, but it never connects that to the `limit` argument itself.

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: what changed between data versions of the server's crawled artifact, scoped to crawl-to-crawl differences in finops.org content. It explicitly disambiguates from a Foundation-published changelog, so the agent knows exactly what this returns and that no sibling tool covers this ground.

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

Usage Guidelines4/5

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

Gives clear context for when this applies (checking crawl-to-crawl diffs in the retained history) and rules out a common misreading ('not a Foundation-published changelog'), plus points to the equivalent resource at finops://framework/meta/changelog. It stops short of an explicit when-to-use/when-not rule against sibling tools, but no sibling offers changelog data.

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

Deploy Server