Skip to main content
Glama
rawtreedb

RawTree MCP Server

Official
by rawtreedb

List Logs

list-logs

Retrieve recent RawTree insert, query, describe, and explain logs to debug errors, verify activity, and view exact SQL executed. Filter by time, type, status, origin, or table.

Instructions

Purpose: List recent RawTree insert/query/describe/explain activity for the configured project.

NOT for: Reading application log files from disk or infrastructure logs. This tool reads RawTree's product query and insert logs.

Returns: Log entries with time, type, status, origin, query, exception, rows, duration, bytes, tables, projections, hints, and pagination.

When to use:

  • An insert or query failed and you need the RawTree exception or hints

  • You need to verify whether an agent, CLI, API, or UI call reached RawTree

  • You need recent activity for a table

  • You want the exact SQL RawTree saw

Workflow: Start with status=error for the last hour. Narrow by table or type if needed. Use next_offset for pagination.

Key trigger phrases: "check RawTree logs", "why did the insert fail", "show query history", "recent errors"

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
startTimeNoInclusive lower bound as an ISO datetime. Defaults to one hour before endTime.
endTimeNoInclusive upper bound as an ISO datetime. Defaults to now.
limitNoNumber of logs to return. Default: 50. Max: 200.
offsetNoNumber of logs to skip for pagination.
searchNoOptional raw RawTree search string, for example "type:insert status:error table:events". Structured filters are appended to it.
typesNoFilter by log type.
statusesNoFilter by status.
originsNoFilter by origin.
tablesNoFilter by one or more table names.
hintsNoFilter to logs with any hints or no hints.
Behavior5/5

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

With no annotations, the description fully discloses that it reads RawTree's product query and insert logs, returns specific fields, and supports pagination. It implies a read-only operation, and no contradictions are present.

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 well-structured with clear sections, front-loaded purpose, and no superfluous content. Every sentence adds value.

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?

For a tool with 10 optional parameters, no annotations, and no output schema, the description effectively explains the return format, pagination, and typical usage. It is complete enough for an agent to use successfully.

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 coverage is 100%, so baseline is 3. The description adds usage workflow (e.g., start with status=error) but does not provide significant new parameter semantics beyond the schema's descriptions.

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 the tool lists 'recent RawTree insert/query/describe/explain activity for the configured project,' specifying verb, resource, and scope. It also distinguishes itself from reading application log files, differentiating it from potential sibling confusion.

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?

The description explicitly states what the tool is NOT for, provides specific 'When to use' scenarios, a suggested workflow, and key trigger phrases. This gives excellent guidance for when to choose this tool over alternatives.

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/rawtreedb/rawtree-mcp'

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