Skip to main content
Glama
rawtreedb

RawTree MCP Server

Official
by rawtreedb
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

List Logs

list-logs

Inspect recent RawTree insert, query, describe, and explain logs to diagnose failures, verify calls, review table history, and get exact SQL with exceptions, hints, and pagination.

Instructions

Purpose: List recent RawTree insert/query/describe/explain activity for a database.

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
hintsNoFilter to logs with any hints or no hints.
limitNoNumber of logs to return. Default: 50. Max: 200.
typesNoFilter by log type.
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.
tablesNoFilter by one or more table names.
clusterNoRawTree cluster to use for this operation.
endTimeNoInclusive upper bound as an ISO datetime. Defaults to now.
originsNoFilter by origin.
databaseNoOptional RawTree database override. RawTree uses the default database when omitted.
statusesNoFilter by status.
startTimeNoInclusive lower bound as an ISO datetime. Defaults to one hour before endTime.
organizationNoRawTree organization containing the target cluster.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv0.3.2
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
    • addedInput schema / properties / cluster
      Added value: +{
+  "description": "RawTree cluster to use for this operation.",
+  "minLength": 1,
+  "type": "string"
+}
    • addedInput schema / properties / database
      Added value: +{
+  "description": "Optional RawTree database override. RawTree uses the default database when omitted.",
+  "minLength": 1,
+  "type": "string"
+}
    • addedInput schema / properties / organization
      Added value: +{
+  "description": "RawTree organization containing the target cluster.",
+  "minLength": 1,
+  "type": "string"
+}
  2. First observedv0.1.0

TDQS

A4.4/5.0
Behavior4/5

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

With no annotations, the description carries the behavioral burden and does well: it lists returned fields, default time window, pagination, origin types, and the exact SQL RawTree saw. It does not state read-only/permission requirements explicitly, and it says 'next_offset' for pagination while the schema exposes an 'offset' input.

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 appropriately sized for a 13-parameter tool and is strongly front-loaded with purpose and exclusions. Bulleted sections keep it scannable, and the trigger phrases aid retrieval without replacing the core semantics.

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 no annotations, no output schema, and 13 optional parameters, the description is largely complete: it covers purpose, exclusions, return fields, and workflow. It still omits permission/authentication context and has the 'next_offset' versus 'offset' naming inconsistency.

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%, so the schema already documents all 13 parameters. The description adds useful workflow guidance for status, table, and type filters, but it does not explain most parameters and introduces a minor mismatch by referencing 'next_offset' instead of the schema's 'offset'.

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?

States a specific verb and resource: list RawTree insert/query/describe/explain activity. It explicitly distinguishes itself from application/infrastructure log reading, so an agent can route correctly without opening the schema.

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?

Provides explicit when-to-use bullets, a suggested workflow, and a clear NOT-for section. It names concrete scenarios such as failed inserts, agent/CLI/API/UI verification, and filtering by table.

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