Skip to main content
Glama
rawtreedb

RawTree MCP Server

Official
by rawtreedb

Insert JSON

insert-json

Insert one JSON object or an array of JSON objects into a RawTree table, which auto-creates the table on first insert.

Instructions

Purpose: Insert one JSON object or an array of JSON objects into a RawTree table. RawTree auto-creates the table on first insert.

NOT for: Loading data from a public URL (use insert-from-url). Not for transformed URL ingest; transforms only apply to JSON request bodies.

Returns: Insert confirmation, usually { "inserted": }. Firehose transform returns request metadata.

When to use:

  • User wants to send events, logs, traces, metrics, or arbitrary records to RawTree

  • You need to create a table by inserting the first row

  • You need to validate that RawTree accepts a payload shape

  • You have OTLP, CloudWatch Logs, CloudTrail, or Firehose JSON that should be flattened by RawTree

Workflow: Choose a table name → send a small representative payload → run describe-table or run-query to verify.

Key trigger phrases: "insert this", "send event", "write to RawTree", "create table with data", "ingest JSON"

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tableYesTarget table name. RawTree accepts identifiers like events, traces, api_logs.
dataYesA JSON object or a non-empty array of JSON objects to insert.
transformNoOptional RawTree built-in transform for JSON body inserts: otlp-traces, otlp-logs, otlp-metrics, cloudwatch-logs, cloudtrail, or firehose.
columnsNoFor transform=firehose only: TSV column names matching each Firehose record line.
Behavior4/5

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

No annotations, so description carries full burden. Discloses auto-creation, return format (insert confirmation with row count), and firehose transform metadata. Missing error conditions and idempotency details.

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?

Structured with headings, bullet points, and clear sections. Front-loaded purpose and conditions. Every sentence adds value without redundancy.

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?

Covers return values, workflow, and trigger phrases given no output schema. Could include more on error states but overall comprehensive for the tool's complexity.

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?

Input schema already provides full parameter descriptions (100% coverage), so description adds limited semantic value beyond contextual workflow guidance like 'send a small representative payload'. Baseline 3 is appropriate.

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?

Description clearly states it inserts JSON objects into RawTree, auto-creates tables, and distinguishes from insert-from-url. Specific verb and resource with clear scope.

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

Usage Guidelines4/5

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

Provides explicit when-to-use scenarios (events, logs, traces) and when-not-to-use (public URL). Lists workflow steps and trigger phrases. Lacks exclusion of other sibling tools like run-query.

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