observability Static interface comparison

Grafana MCP

2.1.1 2.2.0

FAILPending human review

1 new destructive capability requires explicit review.

View the upgrade review as Markdown

A shareable summary of this comparison for an issue, pull request or ticket. Select the text and copy it.

Tools79 → 80
Added1
Removed0
Schema changes6
Input schema changes6
Output schema changes0
Unclassified schema changes0
Description changes10
New write authority0
New destructive authority1
New unknown authority0
AnalysisFAIL

INTERFACE DIFF

What changed, tool by tool

Classification from the recorded findings · definitions from the published snapshots

14 tools with recorded changes

  1. get_dashboard_panel_queriesModifiedSchemaDescriptionREVIEWINFO

    What changed

    • get_dashboard_panel_queries — Schema change: input property added: end.
    • get_dashboard_panel_queries — Schema change: input property added: start.
    • get_dashboard_panel_queries: description changed.

    Why it could matter

    • Calls or consumers built for the earlier schema may need to change.
    • Models choose and call tools partly from their descriptions.

    What to verify

    • Validate representative existing tool calls against the new argument schema.
    • Spot-check that agents still select this tool as intended.
    Declared effect
    read → read
    Description
    PreviousRetrieve panel queries from a Grafana dashboard. Supports all datasource types (Prometheus, Loki, CloudWatch, SQL, etc.) and row-nested panels. Optionally filter to a specific panel by ID with `panelId`. Optionally provide `variables` for template variable substitution, which populates `processedQuery` and `requiredVariables` fields. Returns an array of objects with fields: title, query (raw expression), datasource (object with uid and type), and optionally processedQuery, refId, requiredVariables, and target. Targets built in a visual editor (CloudWatch metric search, InfluxDB query builder) have no string expression: those return an empty query plus `target`, the panel's raw query JSON. They can be executed as panel queries but not as standalone expressions.
    CurrentRetrieve panel queries from a Grafana dashboard. Supports all datasource types (Prometheus, Loki, CloudWatch, SQL, etc.) and row-nested panels. Optionally filter to a specific panel by ID with `panelId`. Provide `variables` (an empty object uses saved selections) or `start`/`end` to populate `processedQuery` and `requiredVariables`. Referenced All selections return `warnings` requesting explicit values. Returns an array of objects with fields: title, query (raw expression), datasource (object with uid and type), and optionally processedQuery, refId, requiredVariables, and target. Targets built in a visual editor (CloudWatch metric search, InfluxDB query builder) have no string expression: those return an empty query plus `target`, the panel's raw query JSON. They can be executed as panel queries but not as standalone expressions.

    Input schema

    PropertyPrevious (2.1.1)Current (2.2.0)Change
    endnot presentstringoptional
    • Added
    startnot presentstringoptional
    • Added
    4 unchanged entries
    • (schema root)
    • panelId
    • uid
    • variables

    No output schema is recorded for this tool in either release.

    Exact JSON from the published snapshots

    Loads the exact recorded definitions of this tool from both releases. The full snapshots are linked under Evidence and provenance.

    Link to this tool
  2. get_tempo_traceModifiedSchemaDescriptionREVIEWINFO

    What changed

    • get_tempo_trace — Schema change: input property added: end.
    • get_tempo_trace — Schema change: input property added: start.
    • get_tempo_trace: description changed.

    Why it could matter

    • Calls or consumers built for the earlier schema may need to change.
    • Models choose and call tools partly from their descriptions.

    What to verify

    • Validate representative existing tool calls against the new argument schema.
    • Spot-check that agents still select this tool as intended.
    Declared effect
    read → read
    Description
    PreviousRetrieve a specific trace by ID
    CurrentRetrieve a specific trace by ID. Returns its spans grouped by service and resource, with span attributes, events and links.

    Input schema

    PropertyPrevious (2.1.1)Current (2.2.0)Change
    endnot presentstringoptional
    • Added
    startnot presentstringoptional
    • Added
    4 unchanged entries
    • (schema root)
    • datasourceUid
    • focus_span_id
    • trace_id

    No output schema is recorded for this tool in either release.

    Exact JSON from the published snapshots

    Loads the exact recorded definitions of this tool from both releases. The full snapshots are linked under Evidence and provenance.

    Link to this tool
  3. list_prometheus_label_namesModifiedSchemaREVIEW

    What changed

    • list_prometheus_label_names — Schema change: input property matches changed: items {"properties":{"fil… → {"oneOf":[{"descrip….

    Why it could matter

    • Calls or consumers built for the earlier schema may need to change.

    What to verify

    • Validate representative existing tool calls against the new argument schema.
    Declared effect
    read → read

    Input schema

    PropertyPrevious (2.1.1)Current (2.2.0)Change
    matches › [items]objectoneOf (2)
    • Changed: oneOf
    • Type changed

    oneOf: — → [{"description":"A Prometheus selector such as {job=\"api\"}","type":"string"},{"properties":{"filters":{"items":{"properties":{"name":{"description":"The name of the label to match against","type":"string"},"type":{"description":"One of th… (truncated: full value in the exact JSON)

    type: "object" → —

    matches › [items] › filtersarrayoptionalnot present
    • Removed
    matches › [items] › filters › [items]objectnot present
    • Removed
    matches › [items] › filters › [items] › namestringrequirednot present
    • Removed
    matches › [items] › filters › [items] › typestringrequirednot present
    • Removed
    matches › [items] › filters › [items] › valuestringrequirednot present
    • Removed
    7 unchanged entries
    • (schema root)
    • datasourceUid
    • endRfc3339
    • limit
    • matches
    • projectName
    • startRfc3339

    No output schema is recorded for this tool in either release.

    Exact JSON from the published snapshots

    Loads the exact recorded definitions of this tool from both releases. The full snapshots are linked under Evidence and provenance.

    Link to this tool
  4. list_prometheus_label_valuesModifiedSchemaREVIEW

    What changed

    • list_prometheus_label_values — Schema change: input property matches changed: items {"properties":{"fil… → {"oneOf":[{"descrip….

    Why it could matter

    • Calls or consumers built for the earlier schema may need to change.

    What to verify

    • Validate representative existing tool calls against the new argument schema.
    Declared effect
    read → read

    Input schema

    PropertyPrevious (2.1.1)Current (2.2.0)Change
    matches › [items]objectoneOf (2)
    • Changed: oneOf
    • Type changed

    oneOf: — → [{"description":"A Prometheus selector such as {job=\"api\"}","type":"string"},{"properties":{"filters":{"items":{"properties":{"name":{"description":"The name of the label to match against","type":"string"},"type":{"description":"One of th… (truncated: full value in the exact JSON)

    type: "object" → —

    matches › [items] › filtersarrayoptionalnot present
    • Removed
    matches › [items] › filters › [items]objectnot present
    • Removed
    matches › [items] › filters › [items] › namestringrequirednot present
    • Removed
    matches › [items] › filters › [items] › typestringrequirednot present
    • Removed
    matches › [items] › filters › [items] › valuestringrequirednot present
    • Removed
    8 unchanged entries
    • (schema root)
    • datasourceUid
    • endRfc3339
    • labelName
    • limit
    • matches
    • projectName
    • startRfc3339

    No output schema is recorded for this tool in either release.

    Exact JSON from the published snapshots

    Loads the exact recorded definitions of this tool from both releases. The full snapshots are linked under Evidence and provenance.

    Link to this tool
  5. query_loki_logsModifiedDescriptionINFO

    What changed

    • query_loki_logs: description changed.

    Why it could matter

    • Models choose and call tools partly from their descriptions.

    What to verify

    • Spot-check that agents still select this tool as intended.
    Declared effect
    read → read
    Description
    PreviousExecutes a log query against a Loki or VictoriaLogs datasource and returns matching log entries (or metric samples on Loki). Defaults to the last hour, a limit of 10 entries, and 'backward' direction (newest first). The `logql` parameter takes LogQL on Loki and LogsQL on VictoriaLogs (e.g., Loki: `{app="foo"} |= "error"`; VictoriaLogs: `{app="foo"} "error"`). To count matching log lines precisely, use a `count_over_time()` metric query with queryType='instant'. For broad queries that match many lines, set `format` to 'compact' to group results by stream and avoid repeating label metadata on every line. If this server enables the Loki cost guardrail, expensive queries are rejected before execution: query cost is bytes SCANNED, determined only by the stream selector and time range — line filters (|=) and parsers (| json) reduce what is returned, not what is scanned. Use a stream selector with at least one selective positive label matcher (never `{}`, `=~".*"`/`=~".+"`, or negative-only matchers), keep time ranges narrow; rejected queries return rewrite guidance.
    CurrentExecutes a log query against a Loki or VictoriaLogs datasource and returns matching log entries (or metric samples on Loki). Defaults to the last hour, a limit of 10 entries, and 'backward' direction (newest first). The `logql` parameter takes LogQL on Loki and LogsQL on VictoriaLogs (e.g., Loki: `{app="foo"} |= "error"`; VictoriaLogs: `{app="foo"} "error"`). To count matching log lines precisely, use a `count_over_time()` metric query with queryType='instant'. For broad queries that match many lines, set `format` to 'compact' to group results by stream and avoid repeating label metadata on every line. Query cost is the bytes scanned, which the index statistics for the stream selector over the same time range estimate before a broad selector or long time range is run. If this server enables the Loki cost guardrail, expensive queries are rejected before execution: query cost is bytes SCANNED, determined only by the stream selector and time range — line filters (|=) and parsers (| json) reduce what is returned, not what is scanned. Use a stream selector with at least one selective positive label matcher (never `{}`, `=~".*"`/`=~".+"`, or negative-only matchers), keep time ranges narrow; rejected queries return rewrite guidance.

    Input schema

    Input schema unchanged.

    10 unchanged entries
    • (schema root)
    • datasourceUid
    • direction
    • endRfc3339
    • format
    • limit
    • logql
    • queryType
    • startRfc3339
    • stepSeconds

    No output schema is recorded for this tool in either release.

    Exact JSON from the published snapshots

    Loads the exact recorded definitions of this tool from both releases. The full snapshots are linked under Evidence and provenance.

    Link to this tool
  6. query_loki_patternsModifiedDescriptionINFO

    What changed

    • query_loki_patterns: description changed.

    Why it could matter

    • Models choose and call tools partly from their descriptions.

    What to verify

    • Spot-check that agents still select this tool as intended.
    Declared effect
    read → read
    Description
    PreviousRetrieves detected log patterns from a Loki datasource for a given stream selector and time range. Returns a list of patterns, each containing a pattern string and a total count of occurrences. Patterns help identify common log structures and anomalies. The `logql` parameter must be a stream selector (e.g., `{job="nginx"}`) and does not support line filters or aggregations. Defaults to the last hour if the time range is omitted. **Not supported on VictoriaLogs** datasources - use a `| stats` pipeline instead.
    CurrentRetrieves detected log patterns from a Loki datasource for a given stream selector and time range. Returns a list of patterns, each containing a pattern string, a total count of occurrences, and a detected `level` when available. Patterns help identify common log structures and anomalies. The `logql` parameter must be a stream selector (e.g., `{job="nginx"}`) and does not support line filters or aggregations. Defaults to the last hour if the time range is omitted. **Not supported on VictoriaLogs** datasources - use a `| stats` pipeline instead.

    Input schema

    Input schema unchanged.

    6 unchanged entries
    • (schema root)
    • datasourceUid
    • endRfc3339
    • logql
    • startRfc3339
    • step

    No output schema is recorded for this tool in either release.

    Exact JSON from the published snapshots

    Loads the exact recorded definitions of this tool from both releases. The full snapshots are linked under Evidence and provenance.

    Link to this tool
  7. query_loki_statsModifiedDescriptionINFO

    What changed

    • query_loki_stats: description changed.

    Why it could matter

    • Models choose and call tools partly from their descriptions.

    What to verify

    • Spot-check that agents still select this tool as intended.
    Declared effect
    read → read
    Description
    PreviousRetrieves index-level statistics about log streams matching a given selector within a Loki or VictoriaLogs datasource and time range. Returns an object containing the count of streams, chunks, entries, and total bytes (e.g., `{"streams": 5, "chunks": 50, "entries": 10000, "bytes": 512000}`). **Important**: the `entries` count reflects storage-level index entries (chunk metadata), NOT the number of individual log lines matching the selector. Counting actual matching log lines requires a `count_over_time()` LogQL metric query. On VictoriaLogs only `entries` is populated; the other fields remain zero. The `logql` parameter **must** be a simple label selector (e.g., `{app="nginx", env="prod"}`) and does not support line filters, parsers, or aggregations. Defaults to the last hour if the time range is omitted.
    CurrentRetrieves index-level statistics about log streams matching a given selector within a Loki or VictoriaLogs datasource and time range. Returns an object containing the count of streams, chunks, entries, and total bytes (e.g., `{"streams": 5, "chunks": 50, "entries": 10000, "bytes": 512000}`). **Important**: the `entries` count reflects storage-level index entries (chunk metadata), NOT the number of individual log lines matching the selector. Counting actual matching log lines requires a `count_over_time()` LogQL metric query. On VictoriaLogs only `entries` is populated; the other fields remain zero. The `logql` parameter **must** be a simple label selector (e.g., `{app="nginx", env="prod"}`) and does not support line filters, parsers, or aggregations. The `bytes` field estimates how much data a log query over the same selector and time range would scan, which is useful to know before running a broad selector or long time range. Defaults to the last hour if the time range is omitted.

    Input schema

    Input schema unchanged.

    5 unchanged entries
    • (schema root)
    • datasourceUid
    • endRfc3339
    • logql
    • startRfc3339

    No output schema is recorded for this tool in either release.

    Exact JSON from the published snapshots

    Loads the exact recorded definitions of this tool from both releases. The full snapshots are linked under Evidence and provenance.

    Link to this tool
  8. query_prometheusModifiedDescriptionINFO

    What changed

    • query_prometheus: description changed.

    Why it could matter

    • Models choose and call tools partly from their descriptions.

    What to verify

    • Spot-check that agents still select this tool as intended.
    Declared effect
    read → read
    Description
    PreviousQuery a PromQL-compatible datasource (Prometheus, Thanos, Mimir, Cloud Monitoring, etc.) using a PromQL expression. Supports instant queries (single point) and range queries (time range). Time: RFC3339 or relative expressions like 'now', 'now-1h'.
    CurrentQuery a PromQL-compatible datasource (Prometheus, Thanos, Mimir, Cloud Monitoring, etc.) using a PromQL expression. Returns data without opening a chart. Supports instant and range queries. Time: RFC3339 or relative expressions like 'now', 'now-1h'.

    Input schema

    Input schema unchanged.

    8 unchanged entries
    • (schema root)
    • datasourceUid
    • endTime
    • expr
    • projectName
    • queryType
    • startTime
    • stepSeconds

    No output schema is recorded for this tool in either release.

    Exact JSON from the published snapshots

    Loads the exact recorded definitions of this tool from both releases. The full snapshots are linked under Evidence and provenance.

    Link to this tool
  9. query_pyroscopeModifiedDescriptionINFO

    What changed

    • query_pyroscope: description changed.

    Why it could matter

    • Models choose and call tools partly from their descriptions.

    What to verify

    • Spot-check that agents still select this tool as intended.
    Declared effect
    read → read
    Description
    Previous Unified Pyroscope query tool for fetching profiles or metrics from Pyroscope. Profile data shows WHICH functions consume resources; metrics data shows WHEN consumption spiked. Use query_type="both" for complete analysis in one call. query_type options (extends Grafana's PyroscopeQueryType): - "profile": returns profile data (shape controlled by format) - "metrics": returns time-series data points - "both" (default): returns both profile and metrics in one response format options (shape of the profile data): - "table" (default): per-function table with flat (self) and cumulative values, ranked by flat - "dot": call graph in Graphviz DOT format; nodes are per source line, so one function may span several nodes
    Current Unified Pyroscope query tool for fetching profiles or metrics from Pyroscope. Profile data shows WHICH functions consume resources; metrics data shows WHEN consumption spiked. Use query_type="both" for complete analysis in one call. query_type options (extends Grafana's PyroscopeQueryType): - "profile": returns profile data (shape controlled by format) - "metrics": returns time-series data points; for cumulative profile types (e.g. CPU time, allocations) each point is a per-second rate over its step, in the reported unit (e.g. "cores" for CPU time) - "both" (default): returns both profile and metrics in one response format options (shape of the profile data): - "table" (default): per-function table with flat (self) and cumulative values, ranked by flat - "dot": call graph in Graphviz DOT format; nodes are per source line, so one function may span several nodes

    Input schema

    Input schema unchanged.

    12 unchanged entries
    • (schema root)
    • data_source_uid
    • end_rfc_3339
    • format
    • group_by
    • group_by › [items]
    • matchers
    • max_node_depth
    • profile_type
    • query_type
    • start_rfc_3339
    • step

    No output schema is recorded for this tool in either release.

    Exact JSON from the published snapshots

    Loads the exact recorded definitions of this tool from both releases. The full snapshots are linked under Evidence and provenance.

    Link to this tool
  10. query_tempo_metricsModifiedDescriptionINFO

    What changed

    • query_tempo_metrics: description changed.

    Why it could matter

    • Models choose and call tools partly from their descriptions.

    What to verify

    • Spot-check that agents still select this tool as intended.
    Declared effect
    read → read
    Description
    PreviousCompute trace-derived metrics using a TraceQL metrics query. The syntax is unlike PromQL. Use type 'instant' for a single value or 'range' for a time series (default). Instant queries over large time ranges may timeout — keep the window under 15 minutes for instant, or use range instead.
    CurrentCompute trace-derived metrics using a TraceQL metrics query. The syntax is unlike PromQL. Use type 'instant' for a single value or 'range' for a time series (default). Instant queries over large time ranges may timeout — keep the window under 15 minutes for instant, or use range instead. Returns each series with its labels and either its samples and exemplars (range) or a single value (instant).

    Input schema

    Input schema unchanged.

    6 unchanged entries
    • (schema root)
    • datasourceUid
    • end
    • query
    • start
    • type

    No output schema is recorded for this tool in either release.

    Exact JSON from the published snapshots

    Loads the exact recorded definitions of this tool from both releases. The full snapshots are linked under Evidence and provenance.

    Link to this tool
  11. render_grafana_appAddedAddedINFO

    What changed

    • New read-only tool render_grafana_app.

    Why it could matter

    • The release adds a capability without declared write authority.

    What to verify

    • Decide whether agents should be offered this tool.
    Declared effect
    — → read

    Input schema

    PropertyPrevious (2.1.1)Current (2.2.0)Change
    (schema root)not presentobject, additionalProperties=false
    • Added
    argumentsnot presentobject, anyOf (2)required
    • Added
    toolNamenot presentstring, enum (2)required
    • Added

    No output schema is recorded for this tool in either release.

    Exact JSON from the published snapshots

    Loads the exact recorded definitions of this tool from both releases. The full snapshots are linked under Evidence and provenance.

    Link to this tool
  12. search_dashboardsModifiedSchemaDescriptionREVIEWINFO

    What changed

    • search_dashboards — Schema change: input property added: folderPath.
    • search_dashboards — Schema change: input property query changed: description "Optional query. Om… → "Optional query. Om….
    • search_dashboards: description changed.

    Why it could matter

    • Calls or consumers built for the earlier schema may need to change.
    • Models choose and call tools partly from their descriptions.

    What to verify

    • Validate representative existing tool calls against the new argument schema.
    • Spot-check that agents still select this tool as intended.
    Declared effect
    read → read
    Description
    PreviousSearch Grafana dashboards by query and/or folderUid, tag, and starred. Returns matching dashboards with title, UID, folder, tags, and URL.
    CurrentSearch Grafana dashboards by query and/or folderUid, folderPath, tag, and starred. Returns matching dashboards with title, UID, folder, folder path, tags, and URL.

    Input schema

    PropertyPrevious (2.1.1)Current (2.2.0)Change
    folderPathnot presentstringoptional
    • Added
    querystringoptionalstringoptional
    • Description changed
    7 unchanged entries
    • (schema root)
    • folderUid
    • limit
    • page
    • starred
    • tag
    • tag › [items]

    No output schema is recorded for this tool in either release.

    Exact JSON from the published snapshots

    Loads the exact recorded definitions of this tool from both releases. The full snapshots are linked under Evidence and provenance.

    Link to this tool
  13. search_tempo_tracesModifiedSchemaDescriptionREVIEWINFO

    What changed

    • search_tempo_traces — Schema change: input property added: limit.
    • search_tempo_traces — Schema change: input property added: spss.
    • search_tempo_traces: description changed.

    Why it could matter

    • Calls or consumers built for the earlier schema may need to change.
    • Models choose and call tools partly from their descriptions.

    What to verify

    • Validate representative existing tool calls against the new argument schema.
    • Spot-check that agents still select this tool as intended.
    Declared effect
    read → read
    Description
    PreviousSearch for traces using TraceQL queries
    CurrentSearch for traces using TraceQL queries. Returns each matching trace with its root service, root span name, start time and duration, and the span sets the query matched. Each span lists its ID, start time, duration and the attributes the query returned, as an object mapping attribute names to values.

    Input schema

    PropertyPrevious (2.1.1)Current (2.2.0)Change
    limitnot presentinteger, default=20optional
    • Added
    spssnot presentinteger, default=3optional
    • Added
    5 unchanged entries
    • (schema root)
    • datasourceUid
    • end
    • query
    • start

    No output schema is recorded for this tool in either release.

    Exact JSON from the published snapshots

    Loads the exact recorded definitions of this tool from both releases. The full snapshots are linked under Evidence and provenance.

    Link to this tool
  14. update_incidentModifiedAuthorityFAIL

    What changed

    • update_incident: declared effect changed from write to destructive.

    Why it could matter

    • An existing tool name now declares stronger authority, so a configuration that allowed it before may allow more now.

    What to verify

    • Re-confirm whether agents should keep access to this tool.
    Declared effect
    write → write

    Input schema

    Input schema unchanged.

    10 unchanged entries
    • (schema root)
    • customFields
    • customFields › [items]
    • customFields › [items] › field
    • customFields › [items] › values
    • customFields › [items] › values › [items]
    • incidentId
    • severity
    • status
    • title

    No output schema is recorded for this tool in either release.

    Exact JSON from the published snapshots

    Loads the exact recorded definitions of this tool from both releases. The full snapshots are linked under Evidence and provenance.

    Link to this tool
66 tools with no recorded change
  • add_activity_to_incident
  • alerting_manage_routing
  • alerting_routing_write
  • alerting_rules_read
  • alerting_rules_write
  • alerting_silences_read
  • alerting_silences_write
  • analyze_loki_labels
  • check_datasources_health
  • create_annotation
  • create_datasource
  • create_folder
  • create_incident
  • create_snapshot
  • delete_annotation
  • delete_snapshot
  • diff_tempo_traces
  • generate_deeplink
  • get_alert_group
  • get_annotation_tags
  • get_annotations
  • get_assertions
  • get_current_oncall_users
  • get_dashboard_by_uid
  • get_dashboard_property
  • get_dashboard_summary
  • get_datasource
  • get_doc
  • get_incident
  • get_oncall_shift
  • get_panel_image
  • get_plugin
  • get_snapshot
  • get_tempo_traceql_docs
  • grafana_api_request
  • install_plugin
  • list_alert_groups
  • list_dashboard_versions
  • list_datasources
  • list_incident_custom_fields
  • list_incidents
  • list_loki_label_names
  • list_loki_label_values
  • list_oncall_schedules
  • list_oncall_teams
  • list_oncall_users
  • list_prometheus_metric_metadata
  • list_prometheus_metric_names
  • list_provisioning_repositories
  • list_pyroscope_label_names
  • list_pyroscope_label_values
  • list_pyroscope_profile_types
  • list_snapshots
  • list_tempo_attribute_names
  • list_tempo_attribute_values
  • query_prometheus_histogram
  • search_docs
  • search_folders
  • search_plugin_information
  • suggest_loki_alloy_label_config
  • update_alert_group
  • update_annotation
  • update_dashboard
  • update_datasource
  • user_info
  • validate_provisioning_file

Evidence and provenance

Static findings
FAIL from Modelara’s automated analysis of the two declared interfaces. A policy outcome, not a security rating or a runtime test.
Human review
Pending human review. No reviewer decision is recorded for this comparison.
Published evidence
Part of Valyd’s published data generation listed in valyd-data-source.json. Published records are not rewritten.
Show provenance and exact files
Comparison
grafana/2.1.1~2.2.0The published comparison identifier.
Analyzer
modelara v0.1.8Policy version not recorded.Analyzed Nov 5, 2026, 2:34 AM UTC.
Distribution
go
Previous release
github.com/grafana/mcp-grafana@2.1.179 tools · published by the registry Oct 20, 2026, 5:35 PM UTC · upstream v2.1.1Artifact integritysha256-1sjk0fV6N0uFFXIYp6iERP/BVdbN8BhUr+IdQEOv1UY=Artifactmcp-grafana_2.1.1_checksums.txtInterface fingerprintsha256:09fd47b7457fbb379c39374ed286a1690b09482abf53366adf89726eb8d20bb5Exact interface snapshot (JSON)
Current release
github.com/grafana/mcp-grafana@2.2.080 tools · published by the registry Nov 2, 2026, 1:00 PM UTC · upstream v2.2.0Artifact integritysha256-UQEVfp6lLBCqd/PFWetqv1qD0eY96hr1V1S6ikI1fsE=Artifactmcp-grafana_2.2.0_checksums.txtInterface fingerprintsha256:6c90f99fefa676ac6de70103153f4d2b1cbacfdce750d6c0fd27c54f9296f211Exact interface snapshot (JSON)

The integrity value or digest identifies the exact artifact that was inspected; it does not show that the package is safe. The interface fingerprint identifies the declared tools and schemas Modelara recorded for that release.

MODELARA ANALYSIS OUTPUT

Interface findings

Analyzed with Modelara v0.1.8 · Nov 5, 2026

Policy failures

1 finding
  • update_incidentFAILChanged

    Declared effect write → destructive

    Authority
    WRITEDESTRUCTIVE

Requires review

6 findings
  • get_dashboard_panel_queriesREVIEWChanged

    Input schema changed

    Show details
    • input property added: end
    • input property added: start
    Authority
    READREAD
    Authority unchanged
  • get_tempo_traceREVIEWChanged

    Input schema changed

    Show details
    • input property added: end
    • input property added: start
    Authority
    READREAD
    Authority unchanged
  • list_prometheus_label_namesREVIEWChanged

    Input schema changed

    Show details
    • input property matches changed: items {"properties":{"fil… → {"oneOf":[{"descrip…
    Authority
    READREAD
    Authority unchanged
  • list_prometheus_label_valuesREVIEWChanged

    Input schema changed

    Show details
    • input property matches changed: items {"properties":{"fil… → {"oneOf":[{"descrip…
    Authority
    READREAD
    Authority unchanged
  • search_dashboardsREVIEWChanged

    Input schema changed

    Show details
    • input property added: folderPath
    • input property query changed: description "Optional query. Om… → "Optional query. Om…
    Authority
    READREAD
    Authority unchanged
  • search_tempo_tracesREVIEWChanged

    Input schema changed

    Show details
    • input property added: limit
    • input property added: spss
    Authority
    READREAD
    Authority unchanged

Informational

11 findings
  • render_grafana_appINFOAdded

    New read-only capability

    Authority
    —READ
  • get_dashboard_panel_queriesINFOChanged

    Description changed

    Authority
    READREAD
    Authority unchanged
  • get_tempo_traceINFOChanged

    Description changed

    Authority
    READREAD
    Authority unchanged
  • query_loki_logsINFOChanged

    Description changed

    Authority
    READREAD
    Authority unchanged
  • query_loki_patternsINFOChanged

    Description changed

    Authority
    READREAD
    Authority unchanged
  • query_loki_statsINFOChanged

    Description changed

    Authority
    READREAD
    Authority unchanged
  • query_prometheusINFOChanged

    Description changed

    Authority
    READREAD
    Authority unchanged
  • query_pyroscopeINFOChanged

    Description changed

    Authority
    READREAD
    Authority unchanged
  • query_tempo_metricsINFOChanged

    Description changed

    Authority
    READREAD
    Authority unchanged
  • search_dashboardsINFOChanged

    Description changed

    Authority
    READREAD
    Authority unchanged
  • search_tempo_tracesINFOChanged

    Description changed

    Authority
    READREAD
    Authority unchanged
What do these results mean?
PASS
No policy-significant interface change detected.
REVIEW
Interface changes require inspection.
FAIL
A policy-significant change was detected.
INVALID
The comparison could not be evaluated reliably.
← Back to Grafana MCP release history