Skip to main content
Glama
Sign In
dremio-mcp-lite

dremio-mcp-lite

by guillaume-galp
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

catalog_browse

Explore Dremio data catalog by listing sources, spaces, folders, and tables. Provide an optional path to view a specific location.

Instructions

Browse Dremio catalog to list sources, spaces, folders, and tables. Optionally provide a path to browse a specific location.

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

Input Schema

NameRequiredDescriptionDefault
pathNoOptional path array to browse (e.g., ["source_name", "folder_name"])

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.9

TDQS

B3.3/5.0
Behavior3/5

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

With no annotations provided, the description carries the burden of disclosing behavior. It communicates that this is a read-only browsing operation and that an optional path narrows the location. It does not mention output format, pagination, error behavior, or what happens when no path is given.

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?

The description is a single concise sentence that states the operation, the resource, and the optional parameter. It is front-loaded and contains no filler or redundant information.

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

Completeness3/5

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

For a simple tool with one optional parameter, the description provides enough to invoke it, but the lack of annotations and output schema means more context would help. It does not describe what a successful response looks like, how deep browsing works, or the behavior at the root catalog level.

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?

The schema already documents the path parameter with full coverage and a helpful description. The tool description adds only that the path lets you browse a specific location, which is consistent but does not significantly extend the semantic meaning beyond the schema.

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 tool browses the Dremio catalog and lists sources, spaces, folders, and tables. It uses a specific verb and resource, making the core purpose understandable. However, it does not explicitly distinguish itself from sibling tools like search_catalog.

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?

The description implies browsing by path but provides no guidance on when to use this tool versus alternatives such as search_catalog or table_preview. There are no explicit when-to-use or when-not-to-use instructions.

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