mcp-for-kibana

Get Visualization

get_visualization

Read-only

Retrieve a Kibana visualization by ID to view its title, chart type, data view, metrics, group_by, and filter query, optionally within a specific space.

Instructions

Get a library visualization: title, chart type, data view, metrics, group_by and filter query.

space targets a Kibana space by id (default: the default space).

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": {
      "visualization_id": "<visualization_id>"
    },
    "name": "get_visualization"
  }
}

Input Schema

Name	Required	Description	Default
`space`	No
`visualization_id`	Yes

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Addedv0.4.0Oct 17, 2026

TDQS

B3.4/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds useful context by listing which attributes a visualization carries, but says nothing about not-found behavior, cross-space lookup, or other operational traits.

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 short sentences, front-loaded with the returned fields and the space-scoping note. Every clause earns its place with no filler.

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 not be detailed, and annotations cover the read-only safety profile. The space default is documented; the only real gap is the undocumented visualization_id parameter and any error/not-found behavior.

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 0%, so the description must carry the load, and it does explain that `space` targets a Kibana space by id with the default space as fallback. However, visualization_id is left entirely undocumented in both description and schema, leaving one of two parameters unexplained.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb (Get) and resource (a library visualization) and enumerates the fields returned (title, chart type, data view, metrics, group_by, filter query), so an agent can tell it retrieves a single saved visualization rather than searching. It does not name the sibling search_visualizations or otherwise differentiate explicitly, which keeps it below a 5.

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

Usage Guidelines2/5

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

No when-to-use or when-not-to-use guidance is given. The 'Get' verb implies single-item retrieval, but nothing tells the agent to use search_visualizations to locate an id first or how this differs from get_dashboard.

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