Skip to main content
Glama
Sign In
elk-mcp

elk-mcp

by cocrates
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

list_layout_options

Retrieve available ELK layout options. Optionally filter by substring matching on option ID or name.

Instructions

List known ELK layout options (id, group, etc.). Optional query filters by substring match on id or name.

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

Input Schema

NameRequiredDescriptionDefault
queryNoCase-insensitive substring filter on option id/name

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It states the tool lists options and filters, which is straightforward. However, it does not disclose whether it is read-only, performance, or access implications. For a simple list tool, this is adequate but not detailed.

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 with no wasted words. The first sentence states the core function, the second adds the filter. Efficient and front-loaded.

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?

Given one parameter, no output schema, and no annotations, the description covers the core purpose and filter behavior. It might benefit from mentioning the return format or default behavior (e.g., returns all options if no query), but it is largely complete for its complexity.

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% for the single parameter. The tool description adds context by mentioning fields like 'id, group, etc.' but largely repeats the schema. Additional meaning is minimal.

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?

The description clearly states 'List known ELK layout options' with a specific verb and resource. It distinguishes from sibling tools like list_algorithms and list_layout_categories by naming the scope. The optional query filter is explicit.

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?

The description indicates when to use the tool (listing layout options) and the optional filter. It does not explicitly exclude use cases or compare to sibling tools, but the context signals and names imply differentiation.

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