Skip to main content
Glama
alilxxey

openobserve-community-mcp

list_dashboards

Retrieve dashboards in your OpenObserve organization. Use filters like folder, title, page size, or include raw data to find and manage monitoring dashboards.

Instructions

List dashboards in the current organization.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
folderNo
titleNo
page_sizeNo
include_rawNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The MCP tool handler function `list_dashboards` decorated with @server.tool(). It accepts optional folder, title, page_size, and include_raw parameters, calls the client's list_dashboards method, and formats the result via build_list_dashboards_result.
    @server.tool()
    def list_dashboards(
        folder: str | None = None,
        title: str | None = None,
        page_size: int | None = None,
        include_raw: bool = False,
    ) -> dict[str, Any]:
        """List dashboards in the current organization."""
        client = client_provider.get()
        raw = client.list_dashboards(folder=folder, title=title, page_size=page_size)
        return build_list_dashboards_result(
            org_id=client.resolve_org_id(),
            raw=raw,
            include_raw=include_raw,
        )
  • The schema/parameters for the tool: folder (optional str), title (optional str), page_size (optional int), include_raw (optional bool, default False).
        folder: str | None = None,
        title: str | None = None,
        page_size: int | None = None,
        include_raw: bool = False,
    ) -> dict[str, Any]:
  • The HTTP client method `list_dashboards` that sends a GET request to /api/{org_id}/dashboards with optional query params (folder, title, pageSize).
    def list_dashboards(
        self,
        *,
        folder: str | None = None,
        title: str | None = None,
        page_size: int | None = None,
    ) -> Any:
        query: dict[str, str | int | float | bool] = {}
        if folder:
            query["folder"] = folder
        if title:
            query["title"] = title
        if page_size is not None:
            query["pageSize"] = page_size
    
        return self.request_json(
            "GET",
            self._org_path("/api/{org_id}/dashboards"),
            query=query or None,
        )
  • The output builder `build_list_dashboards_result` that shapes the raw API response into a compact result dict with org_id, count, and dashboards list.
    def build_list_dashboards_result(
        *,
        org_id: str,
        raw: Any,
        include_raw: bool,
    ) -> dict[str, Any]:
        items = raw.get("dashboards", []) if isinstance(raw, dict) else []
        result: dict[str, Any] = {
            "org_id": org_id,
            "count": len(items),
            "dashboards": items,
        }
        return maybe_include_raw(result, raw, include_raw)
  • The tool is registered via the @server.tool() decorator on the `list_dashboards` function inside `create_server()`.
    @server.tool()
    def list_dashboards(
        folder: str | None = None,
        title: str | None = None,
        page_size: int | None = None,
        include_raw: bool = False,
    ) -> dict[str, Any]:
        """List dashboards in the current organization."""
        client = client_provider.get()
        raw = client.list_dashboards(folder=folder, title=title, page_size=page_size)
        return build_list_dashboards_result(
            org_id=client.resolve_org_id(),
            raw=raw,
            include_raw=include_raw,
        )
Behavior2/5

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

With no annotations, the description must disclose behavioral traits like read-only nature, pagination, or side effects. It only says 'list', which implies read-only, but provides no details on rate limits, data format, or scope beyond 'current organization'.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single concise sentence, but it is under-specified for a tool with four parameters. It lacks structure and does not earn its place by adding sufficient value.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given 0% schema coverage and no annotations, the description is incomplete. It omits parameter explanations and behavioral context. While output schema exists, the description still fails to address usage and parameter details.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, yet the description adds no explanation for any of the four parameters (folder, title, page_size, include_raw). It provides no semantics beyond what the schema types and defaults convey.

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?

The description clearly states the verb 'list' and resource 'dashboards' with scope 'in the current organization'. It distinguishes from sibling 'get_dashboard' by implying listing many rather than one, though not explicitly.

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 guidance is given on when to use this tool versus siblings like 'get_dashboard' or other listing tools. The description does not specify prerequisites or context.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/alilxxey/openobserve-community-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server