Skip to main content
Glama
Sign In
Databar MCP Server

Databar MCP Server

Official
by databar-ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

run_table_exporter

Trigger a table exporter to process rows based on selection strategy: run all rows, skip completed rows, or rerun errors.

Instructions

Trigger an exporter to run on a table. By default runs on all rows. Use run_strategy to control row selection. Subject to spending limits.

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": {
      "table_uuid": "<table_uuid>",
      "exporter_id": "<exporter_id>"
    },
    "name": "run_table_exporter"
  }
}

Input Schema

NameRequiredDescriptionDefault
table_uuidYesThe UUID of the table
exporter_idYesThe table exporter ID to run (returned by add_table_exporter)
run_strategyNoWhich rows to process: 'run_all' (default) runs every row, 'run_empty' skips rows that already have a result, 'run_errors' reruns only rows that ended with an error.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.4.0

TDQS

B3.4/5.0
Behavior2/5

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

No annotations provided. Description only mentions spending limits, but fails to disclose sync/async nature, return value, error handling, or authorization requirements. Minimal behavioral context.

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?

Two concise sentences, front-loaded with purpose. No unnecessary words or repetition.

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

Completeness2/5

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

No output schema. Missing critical details: return format, asynchronous behavior, error scenarios, rate limits. For a trigger tool with no annotations, this is insufficient.

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 has 100% coverage, so baseline is 3. Description adds minor value for run_strategy but no additional context for table_uuid or exporter_id. Marginal improvement over schema.

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 action ('trigger an exporter to run on a table'), with a specific verb and resource. It distinctly separates from sibling tools like add_table_exporter (add vs run).

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?

Mentions default behavior and run_strategy options, but lacks explicit guidance on when not to use this tool or how it differs from run_enrichment/run_waterfall. Adequate but incomplete.

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