Skip to main content
Glama
Sign In

Spaces by Peakflo

by ai.peakflo
OverviewDiscussionsAdmin

table_bulk_insert

Insert multiple rows into a data table in a single batch operation.

All rows must have the same columns. Maximum 10,000 rows per call. The operation is atomic — all rows are inserted or none are.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "tableId": "<tableId>",
      "rows": "<rows>"
    },
    "name": "table_bulk_insert"
  }
}

Input Schema

NameRequiredDescriptionDefault
rowsYesJSON array of row objects to insert, e.g. [{"name": "A", "amount": 100}, {"name": "B", "amount": 200}]
tableIdYesThe data table ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

The annotations only declare non-read-only, non-destructive, closed-world; the description adds real behavioral context beyond that — atomic all-or-nothing semantics, a hard 10,000-row ceiling, and the uniform-columns precondition. These are the constraints an agent must design around. It stops short of describing error behavior or what is returned on success, which keeps it from a 5.

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?

Four short sentences, front-loaded with the core action and then layering the constraints that matter. Every sentence carries a distinct rule (uniform columns, row cap, atomicity) with no repetition of the schema or annotations.

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?

For a two-parameter mutation tool with no output schema, the description covers the operational contract well: batching, limits, homogeneity, and transactionality. It omits what a successful call returns (inserted count, generated IDs) and how schema or type mismatches surface as errors, which an agent would still need to discover.

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%, so the baseline is 3, and the description earns a bump by adding meaning the schema does not: rows must share the same column set and the total is capped at 10,000. It adds no guidance on the tableId parameter or on how mismatched schemas are rejected, so it is not fully compensating.

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 states a specific verb and resource ('Insert multiple rows into a data table') with explicit batch scope in a single call. It is clear what the tool does, but it never distinguishes itself from the sibling table_insert (single-row insert), leaving the agent to infer the batch/single split from the name alone.

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

Usage Guidelines3/5

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

Usage is only implied: 'multiple rows' and 'single batch operation' suggest this is the batch counterpart to table_insert, and the 10,000-row cap implies a fallback for larger loads. However, no sentence explicitly says when to prefer this over table_insert or what to do above the row limit.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Spaces by Peakflo toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources