Skip to main content
Glama

list_tables

Lists tables and views in the loaded Perfetto trace, optionally filtered by a GLOB pattern. Use to explore schema or verify table names before querying.

Instructions

List tables and views in the loaded trace. Read-only.

Use when: exploring an unfamiliar trace or verifying a table exists before writing SQL. Underlying SQL engine is SQLite, so the catalog tables common in other SQL engines aren't present — this MCP tool is the schema introspection path.

Don't use for: queries against known stdlib modules — go straight to execute_sql with INCLUDE PERFETTO MODULE. Don't reference this tool name inside SQL; it's a separate MCP tool, not a SQL function — call it via the tool API.

Parameters: optional pattern — SQLite GLOB filter (e.g. chrome_* for chrome stdlib views, slice* for the slice table family). Without it, internal stdlib tables (_*) are hidden.

Empty result: no tables matched the pattern. If a doc-listed table is missing, retry with an explicit pattern in case it's marked internal.

Errors when: no trace is loaded — call load_trace first.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
patternNoOptional GLOB pattern to filter table names (e.g. "chrome_*").
Behavior5/5

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

No annotations exist, so description fully covers behavior: read-only, hidden internal tables when no pattern, empty result meaning, and error when no trace loaded. Provides clear expectations.

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?

Description is well-structured and concise: front-loads purpose and read-only flag, then uses bullet-like sections ('Use when:', 'Don't use for:') for clear guidance. No unnecessary words.

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

Completeness5/5

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

With one optional parameter, no output schema, and no annotations, the description fully covers all needed context: usage, parameter behavior, error conditions, empty result handling. Complete for the tool's complexity.

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

Parameters4/5

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

Schema coverage is 100% (only one parameter 'pattern'), but description adds important context beyond JSON Schema: explains pattern is a SQLite GLOB filter, gives examples (chrome_*, slice*), and describes default behavior (hides _* tables).

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 states 'List tables and views in the loaded trace. Read-only.' It uses a specific verb ('list') and resource ('tables and views'), and distinguishes from siblings like 'execute_sql' by noting this is for schema introspection.

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

Usage Guidelines5/5

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

Explicitly provides use cases: 'Use when: exploring an unfamiliar trace or verifying a table exists before writing SQL.' Also states when not to use: 'Don't use for: queries against known stdlib modules — go straight to execute_sql with INCLUDE PERFETTO MODULE.' Advises against referencing tool name in SQL.

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/tooluse-labs/perfetto-mcp-rs'

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