observability Static interface comparison

Grafana MCP

2.2.0 2.3.0

REVIEWPending human review

8 schema changes require review.No new authority detected.

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.

Tools80 → 80
Added0
Removed0
Schema changes8
Input schema changes8
Output schema changes0
Unclassified schema changes0
Description changes5
New write authority0
New destructive authority0
New unknown authority0
AnalysisREVIEW

INTERFACE DIFF

What changed, tool by tool

Classification from the recorded findings · definitions from the published snapshots

14 tools with recorded changes

  1. alerting_rules_writeModifiedSchemaREVIEW

    What changed

    • alerting_rules_write — Schema change: input property removed: label_selectors.
    • alerting_rules_write — Schema change: input property removed: limit_alerts.
    • alerting_rules_write — Schema change: input property removed: matchers.
    • alerting_rules_write — Schema change: input property removed: rule_limit.
    • alerting_rules_write — Schema change: input property removed: rule_type.
    • alerting_rules_write — Schema change: input property removed: search_folder.
    • alerting_rules_write — Schema change: input property removed: search_rule_name.
    • alerting_rules_write — Schema change: input property removed: states.
    • alerting_rules_write — Schema change: input property datasource_uid changed: description "Datasource UID for… → "Datasource UID for….
    • alerting_rules_write — Schema change: input property folder_uid changed: description "The folder UID. Fo… → "The folder UID. Re….
    • alerting_rules_write — Schema change: input property notification_settings changed: description "Notification setti… → "Notification setti….
    • alerting_rules_write — Schema change: input property operation changed: description "The operation to p… → "The operation to p…, enum ["list","get","vers… → ["create","update",….
    • alerting_rules_write — Schema change: input property rule_uid changed: description "The UID of the ale… → "The UID of the ale….

    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
    write → write

    Input schema

    PropertyPrevious (2.2.0)Current (2.3.0)Change
    datasource_uidstringoptionalstringoptional
    • Description changed
    folder_uidstringoptionalstringoptional
    • Description changed
    label_selectorsarrayoptionalnot present
    • Removed
    label_selectors › [items]stringnot present
    • Removed
    limit_alertsintegeroptionalnot present
    • Removed
    matchersarrayoptionalnot present
    • Removed
    matchers › [items]stringnot present
    • Removed
    notification_settingsobjectoptionalobjectoptional
    • Description changed
    operationstring, enum (6)requiredstring, enum (3)required
    • Description changed
    • Constraint: enum

    enum: ["list","get","versions","create","update","delete"] → ["create","update","delete"]

    rule_limitinteger, default=200optionalnot present
    • Removed
    rule_typestring, enum (2)optionalnot present
    • Removed
    rule_uidstringoptionalstringoptional
    • Description changed
    search_folderstringoptionalnot present
    • Removed
    search_rule_namestringoptionalnot present
    • Removed
    statesarrayoptionalnot present
    • Removed
    states › [items]stringnot present
    • Removed
    21 unchanged entries
    • (schema root)
    • annotations
    • condition
    • data
    • data › [items]
    • disable_provenance
    • evaluation_interval
    • exec_err_state
    • expression
    • for
    • is_paused
    • keep_firing_for
    • labels
    • managed_by
    • missing_series_evals_to_resolve
    • namespace
    • no_data_state
    • org_id
    • record
    • rule_group
    • 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
  2. alerting_silences_writeModifiedSchemaREVIEW

    What changed

    • alerting_silences_write — Schema change: input property removed: rule_uid.
    • alerting_silences_write — Schema change: input property matchers changed: description "Label matchers. Re… → "Label matchers. Re….
    • alerting_silences_write — Schema change: input property operation changed: description "The operation to p… → "The operation to p…, enum ["list","get","crea… → ["create","update",….
    • alerting_silences_write — Schema change: input property silence_id changed: description "The silence id (re… → "The silence id (re….
    • alerting_silences_write — Schema change: input property starts_at changed: description "Silence start time… → "Silence start time….

    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
    write → write

    Input schema

    PropertyPrevious (2.2.0)Current (2.3.0)Change
    matchersarrayoptionalarrayoptional
    • Description changed
    operationstring, enum (5)requiredstring, enum (3)required
    • Description changed
    • Constraint: enum

    enum: ["list","get","create","update","delete"] → ["create","update","delete"]

    rule_uidstringoptionalnot present
    • Removed
    silence_idstringoptionalstringoptional
    • Description changed
    starts_atstringoptionalstringoptional
    • Description changed
    9 unchanged entries
    • (schema root)
    • comment
    • created_by
    • ends_at
    • matchers › [items]
    • matchers › [items] › isEqual
    • matchers › [items] › isRegex
    • matchers › [items] › name
    • matchers › [items] › value

    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. create_datasourceModifiedSchemaDescriptionMetadataREVIEWINFO

    What changed

    • create_datasource — Schema change: input property name changed: description "Datasource display… → "Datasource display….
    • create_datasource — No longer required: name.
    • create_datasource: description changed.
    • create_datasource: declared metadata changed (declared open_world: false → true).

    Why it could matter

    • Calls or consumers built for the earlier schema may need to change.
    • Existing calls stay valid in shape, but behavior when the argument is omitted may differ.
    • Models choose and call tools partly from their descriptions.
    • Annotations such as idempotent or open-world hints can inform how clients treat a tool.

    What to verify

    • Validate representative existing tool calls against the new argument schema.
    • Confirm the server’s behavior when the argument is omitted.
    • Spot-check that agents still select this tool as intended.
    • Confirm any client logic that relies on these annotations.
    Declared effect
    write → write
    Description
    PreviousCreate a datasource in two steps. Called with only the type, it returns the plugin's field schema and creates nothing. Called with the type, the display name in the top-level name argument, schemaReviewed=true, and field values in the fields map, it creates the datasource. The plugin for the type must already be installed. Secrets (passwords, tokens) are not accepted. Returns UID, health check, and a config page link.
    CurrentCreate a datasource in two steps. Called with only the type, it returns the fields to fill in and creates nothing. Called again with the type, a display name in name, and the field values, it creates the datasource; for a type with a field schema, put the values in the fields map and set schemaReviewed=true. The plugin for the type must already be installed. Secrets (passwords, tokens) can't be set. Returns the UID, the result of a health check against the new datasource, and a config page link.

    Input schema

    PropertyPrevious (2.2.0)Current (2.3.0)Change
    namestringrequiredstringoptional
    • No longer required
    • Description changed
    10 unchanged entries
    • (schema root)
    • access
    • basicAuth
    • database
    • fields
    • isDefault
    • schemaReviewed
    • type
    • url
    • withCredentials

    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. create_snapshotModifiedMetadataINFO

    What changed

    • create_snapshot: declared metadata changed (declared open_world: false → true).

    Why it could matter

    • Annotations such as idempotent or open-world hints can inform how clients treat a tool.

    What to verify

    • Confirm any client logic that relies on these annotations.
    Declared effect
    write → write

    Input schema

    Input schema unchanged.

    7 unchanged entries
    • (schema root)
    • dashboard
    • deleteKey
    • expires
    • external
    • key
    • name

    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. get_dashboard_panel_queriesModifiedDescriptionINFO

    What changed

    • get_dashboard_panel_queries: 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
    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`. 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.
    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, and variables saved without a value, 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

    Input schema unchanged.

    6 unchanged entries
    • (schema root)
    • end
    • panelId
    • start
    • 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
  6. grafana_api_requestModifiedDescriptionINFO

    What changed

    • grafana_api_request: 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
    write → write
    Description
    PreviousMake an authenticated HTTP request to the Grafana API. Similar to 'gh api' for GitHub. Supports any Grafana API endpoint with optional jq-style response filtering. Use this for API endpoints that don't have a dedicated tool.
    CurrentMake an authenticated HTTP request to the Grafana API. Supports any Grafana API endpoint with optional jq-style response filtering. Use this for API endpoints that don't have a dedicated tool.

    Input schema

    Input schema unchanged.

    6 unchanged entries
    • (schema root)
    • body
    • endpoint
    • headers
    • jq
    • method

    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. list_dashboard_versionsModifiedSchemaREVIEW

    What changed

    • list_dashboard_versions — Schema change: input property start changed: description "Version to start f… → "Number of newest v….

    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.2.0)Current (2.3.0)Change
    startinteger, minimum=1optionalinteger, minimum=1optional
    • Description changed
    3 unchanged entries
    • (schema root)
    • limit
    • uid

    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. list_pyroscope_label_namesModifiedSchemaREVIEW

    What changed

    • list_pyroscope_label_names — Schema change: input property matchers changed: +description="Optionally, Promet….

    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.2.0)Current (2.3.0)Change
    matchersstringoptionalstringoptional
    • Description changed
    4 unchanged entries
    • (schema root)
    • data_source_uid
    • end_rfc_3339
    • start_rfc_3339

    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. list_tempo_attribute_namesModifiedSchemaREVIEW

    What changed

    • list_tempo_attribute_names — Schema change: input property added: end.
    • list_tempo_attribute_names — Schema change: input property added: start.

    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.2.0)Current (2.3.0)Change
    endnot presentstringoptional
    • Added
    startnot presentstringoptional
    • Added
    3 unchanged entries
    • (schema root)
    • datasourceUid
    • scope

    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. list_tempo_attribute_valuesModifiedSchemaREVIEW

    What changed

    • list_tempo_attribute_values — Schema change: input property added: end.
    • list_tempo_attribute_values — Schema change: input property added: start.

    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.2.0)Current (2.3.0)Change
    endnot presentstringoptional
    • Added
    startnot presentstringoptional
    • Added
    4 unchanged entries
    • (schema root)
    • datasourceUid
    • filter-query
    • name

    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. query_loki_logsModifiedSchemaREVIEW

    What changed

    • query_loki_logs — Schema change: input property queryType changed: description "Query type: 'range… → "Query type: 'range….

    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.2.0)Current (2.3.0)Change
    queryTypestringoptionalstringoptional
    • Description changed
    9 unchanged entries
    • (schema root)
    • datasourceUid
    • direction
    • endRfc3339
    • format
    • limit
    • logql
    • 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
  12. search_plugin_informationModifiedDescriptionINFO

    What changed

    • search_plugin_information: 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
    PreviousSearch the Grafana plugin catalog by keyword, purpose, or partial name (e.g. 'azure monitoring', 'loki', 'database'). Returns results sorted by trust: official Grafana Labs plugins first, then commercial partner plugins, then community plugins, each with its exact pluginId. Results include warnings for enterprise-only or Angular-based plugins.
    CurrentSearch the Grafana plugin catalog by keyword, purpose, or partial name (e.g. 'azure monitoring', 'loki', 'database'). Returns results ordered by signature type (Grafana Labs, commercial, community), each with its exact pluginId. Results include warnings for enterprise-only or Angular-based plugins.

    Input schema

    Input schema unchanged.

    2 unchanged entries
    • (schema root)
    • query

    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. update_dashboardModifiedDescriptionINFO

    What changed

    • update_dashboard: 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
    write → write
    Description
    PreviousCreate or update a dashboard. Returns the saved dashboard UID and dashboard link in the 'url' field, using the instance public URL when available. Two modes: (1) Full JSON — provide 'dashboard' for new dashboards or complete replacements. (2) Patch — provide 'uid' + 'operations' to make targeted changes to an existing dashboard. One of these two modes is required; 'folderUid', 'message', and 'overwrite' are supplementary and do nothing on their own. Dashboard authoring guidance: if a saved query must support one, many, or All values from a multi-select variable inside a regex expression or matcher, save '${var:regex}' rather than plain '$var'. Saved dashboard annotation queries/definitions live in dashboard JSON under 'annotations.list'; annotation events are stored separately and are not part of the dashboard JSON. For stat panels over the current dashboard range, make the query return the range-level result the stat should display; panel-side reduction only reduces returned series and does not compute peak-over-range or ratio-of-peaks semantics for you. Patch operations support JSONPaths like '$.panels[0].targets[0].expr', '$.panels[1].title', '$.panels[2].targets[0].datasource', '$.templating.list/-', and '$.annotations.list/-'. Append to arrays with '/- ' syntax: '$.panels/- '. Remove by index: {"op": "remove", "path": "$.panels[2]"}. Multiple removes on the same array are automatically reordered to avoid index-shifting issues. Note: only numeric array indices are supported in patch paths; filter expressions like [?(@.id==2)] and wildcards like [*] are not supported. Schema: prefer v2 for new dashboards; if this Grafana lacks v2 the save fails saying so, then send v1. Keep an existing dashboard in its stored schema (indicated by 'isV2'/'apiVersion' on the fetched dashboard). A body with top-level 'elements'/'layout' is saved as v2. Minimal v2 body: {"title":"T","timeSettings":{"from":"now-6h","to":"now"},"variables":[],"elements":{"p1":{"kind":"Panel","spec":{"id":1,"title":"Up","vizConfig":{"kind":"VizConfig","group":"timeseries","spec":{}},"data":{"kind":"QueryGroup","spec":{"queries":[{"kind":"PanelQuery","spec":{"refId":"A","query":{"kind":"DataQuery","group":"prometheus","datasource":{"name":"<ds uid>"},"spec":{"expr":"up"}}}}]}}}}},"layout":{"kind":"GridLayout","spec":{"items":[{"kind":"GridLayoutItem","spec":{"x":0,"y":0,"width":24,"height":8,"element":{"kind":"ElementReference","name":"p1"}}}]}}}. For tabs, layout is {"kind":"TabsLayout","spec":{"tabs":[{"kind":"TabsLayoutTab","spec":{"title":"A","layout":<GridLayout>}}]}}.
    CurrentCreate or update a dashboard. Returns the saved dashboard UID and dashboard link in the 'url' field, using the instance public URL when available. Two modes: (1) Full JSON — provide 'dashboard' for new dashboards or complete replacements. (2) Patch — provide 'uid' + 'operations' to make targeted changes to an existing dashboard. One of these two modes is required; 'folderUid', 'message', and 'overwrite' are supplementary and do nothing on their own. Dashboard authoring guidance: if a saved query must support one, many, or All values from a multi-select variable inside a regex expression or matcher, save '${var:regex}' rather than plain '$var'. Saved dashboard annotation queries/definitions live in dashboard JSON under 'annotations.list'; annotation events are stored separately and are not part of the dashboard JSON. For stat panels over the current dashboard range, make the query return the range-level result the stat should display; panel-side reduction only reduces returned series and does not compute peak-over-range or ratio-of-peaks semantics for you. Patch operations support JSONPaths like '$.panels[0].targets[0].expr', '$.panels[1].title', '$.panels[2].targets[0].datasource', '$.templating.list/-', and '$.annotations.list/-'. Append to arrays with '/- ' syntax: '$.panels/- '. Remove by index: {"op": "remove", "path": "$.panels[2]"}. Multiple removes on the same array are automatically reordered to avoid index-shifting issues. Note: only numeric array indices are supported in patch paths; filter expressions like [?(@.id==2)] and wildcards like [*] are not supported. Schema: prefer v2 for new dashboards; if this Grafana lacks v2 the save fails saying so, then send v1. Keep an existing dashboard in its stored schema (indicated by 'isV2'/'apiVersion' on the fetched dashboard). A body with top-level 'elements'/'layout' is saved as v2. Send list fields as [] when empty; the server fills links, tags, variables and each panel's links and transformations if omitted. Minimal v2 body: {"title":"T","timeSettings":{"from":"now-6h","to":"now"},"variables":[],"links":[],"elements":{"p1":{"kind":"Panel","spec":{"id":1,"title":"Up","vizConfig":{"kind":"VizConfig","group":"timeseries","spec":{}},"data":{"kind":"QueryGroup","spec":{"queries":[{"kind":"PanelQuery","spec":{"refId":"A","query":{"kind":"DataQuery","group":"prometheus","datasource":{"name":"<ds uid>"},"spec":{"expr":"up"}}}}],"transformations":[]}}}}},"layout":{"kind":"GridLayout","spec":{"items":[{"kind":"GridLayoutItem","spec":{"x":0,"y":0,"width":24,"height":8,"element":{"kind":"ElementReference","name":"p1"}}}]}}}. For tabs, layout is {"kind":"TabsLayout","spec":{"tabs":[{"kind":"TabsLayoutTab","spec":{"title":"A","layout":<GridLayout>}}]}}.

    Input schema

    Input schema unchanged.

    12 unchanged entries
    • (schema root)
    • dashboard
    • folderUid
    • message
    • operations
    • operations › [items]
    • operations › [items] › op
    • operations › [items] › path
    • operations › [items] › value
    • overwrite
    • uid
    • userId

    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_datasourceModifiedMetadataINFO

    What changed

    • update_datasource: declared metadata changed (declared open_world: false → true).

    Why it could matter

    • Annotations such as idempotent or open-world hints can inform how clients treat a tool.

    What to verify

    • Confirm any client logic that relies on these annotations.
    Declared effect
    write → write

    Input schema

    Input schema unchanged.

    11 unchanged entries
    • (schema root)
    • access
    • basicAuth
    • database
    • fields
    • isDefault
    • jsonData
    • name
    • schemaReviewed
    • uid
    • url

    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_silences_read
  • analyze_loki_labels
  • check_datasources_health
  • create_annotation
  • create_folder
  • create_incident
  • 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_trace
  • get_tempo_traceql_docs
  • install_plugin
  • list_alert_groups
  • 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_label_names
  • list_prometheus_label_values
  • list_prometheus_metric_metadata
  • list_prometheus_metric_names
  • list_provisioning_repositories
  • list_pyroscope_label_values
  • list_pyroscope_profile_types
  • list_snapshots
  • query_loki_patterns
  • query_loki_stats
  • query_prometheus
  • query_prometheus_histogram
  • query_pyroscope
  • query_tempo_metrics
  • render_grafana_app
  • search_dashboards
  • search_docs
  • search_folders
  • search_tempo_traces
  • suggest_loki_alloy_label_config
  • update_alert_group
  • update_annotation
  • update_incident
  • user_info
  • validate_provisioning_file

Evidence and provenance

Static findings
REVIEW 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.2.0~2.3.0The published comparison identifier.
Analyzer
modelara v0.1.8Policy version not recorded.Analyzed Nov 11, 2026, 1:20 AM UTC.
Distribution
go
Previous 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)
Current release
github.com/grafana/mcp-grafana@2.3.080 tools · published by the registry Nov 10, 2026, 5:45 PM UTC · upstream v2.3.0Artifact integritysha256-KzMqlyk2+lJPgQUdRn6uJNmCAvzs/17KAR2tEFAh4l4=Artifactmcp-grafana_2.3.0_checksums.txtInterface fingerprintsha256:c08fb18259d52f1a5941303ad6185d1c75bf357525fbf6e6052b68597b350e94Exact 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 11, 2026

Requires review

8 findings
  • alerting_rules_writeREVIEWChanged

    Input schema changed

    Show details
    • input property removed: label_selectors
    • input property removed: limit_alerts
    • input property removed: matchers
    • input property removed: rule_limit
    • input property removed: rule_type
    • input property removed: search_folder
    • input property removed: search_rule_name
    • input property removed: states
    • input property datasource_uid changed: description "Datasource UID for… → "Datasource UID for…
    • input property folder_uid changed: description "The folder UID. Fo… → "The folder UID. Re…
    • input property notification_settings changed: description "Notification setti… → "Notification setti…
    • input property operation changed: description "The operation to p… → "The operation to p…, enum ["list","get","vers… → ["create","update",…
    • input property rule_uid changed: description "The UID of the ale… → "The UID of the ale…
    Authority
    DESTRUCTIVEDESTRUCTIVE
    Authority unchanged
  • alerting_silences_writeREVIEWChanged

    Input schema changed

    Show details
    • input property removed: rule_uid
    • input property matchers changed: description "Label matchers. Re… → "Label matchers. Re…
    • input property operation changed: description "The operation to p… → "The operation to p…, enum ["list","get","crea… → ["create","update",…
    • input property silence_id changed: description "The silence id (re… → "The silence id (re…
    • input property starts_at changed: description "Silence start time… → "Silence start time…
    Authority
    DESTRUCTIVEDESTRUCTIVE
    Authority unchanged
  • create_datasourceREVIEWChanged

    Input schema changed

    Show details
    • input property name changed: description "Datasource display… → "Datasource display…
    • input required: [name, type] → [type]
    Authority
    WRITEWRITE
    Authority unchanged
  • list_dashboard_versionsREVIEWChanged

    Input schema changed

    Show details
    • input property start changed: description "Version to start f… → "Number of newest v…
    Authority
    READREAD
    Authority unchanged
  • list_pyroscope_label_namesREVIEWChanged

    Input schema changed

    Show details
    • input property matchers changed: +description="Optionally, Promet…
    Authority
    READREAD
    Authority unchanged
  • list_tempo_attribute_namesREVIEWChanged

    Input schema changed

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

    Input schema changed

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

    Input schema changed

    Show details
    • input property queryType changed: description "Query type: 'range… → "Query type: 'range…
    Authority
    READREAD
    Authority unchanged

Informational

8 findings
  • create_datasourceINFOChanged

    Description changed

    Authority
    WRITEWRITE
    Authority unchanged
  • get_dashboard_panel_queriesINFOChanged

    Description changed

    Authority
    READREAD
    Authority unchanged
  • grafana_api_requestINFOChanged

    Description changed

    Authority
    DESTRUCTIVEDESTRUCTIVE
    Authority unchanged
  • search_plugin_informationINFOChanged

    Description changed

    Authority
    READREAD
    Authority unchanged
  • update_dashboardINFOChanged

    Description changed

    Authority
    DESTRUCTIVEDESTRUCTIVE
    Authority unchanged
  • create_datasourceINFOChanged

    Metadata changed

    Show details
    • declared open_world: false → true
    Authority
    WRITEWRITE
    Authority unchanged
  • create_snapshotINFOChanged

    Metadata changed

    Show details
    • declared open_world: false → true
    Authority
    WRITEWRITE
    Authority unchanged
  • update_datasourceINFOChanged

    Metadata changed

    Show details
    • declared open_world: false → true
    Authority
    DESTRUCTIVEDESTRUCTIVE
    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