Skip to main content
Glama

create_source

Create a data source for Tares to begin ingesting data immediately without restarting; specify connector, config, and optional project.

Instructions

Create a data source so Tares starts ingesting it immediately (no restart). config is the connector's config (see list_connectors / discover_source); push connectors ignore poll. project is the project id the source joins (default: the default project); other projects can use it too. Returns {ok, name} or an error detail. After creating, use list_sources to watch it ingest and catalog_describe("source:") to see its labels.

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": {
      "name": "<name>",
      "connector": "<connector>",
      "config": "<config>"
    },
    "name": "create_source"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes
pollNo5s
configYes
projectNo
connectorYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.57.0

TDQS

A4.3/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses the immediate-ingestion/no-restart behavior, that push connectors ignore `poll`, the default project behavior, and the minimal return shape. It does not mention auth requirements, failure modes beyond 'an error detail', or whether creation is idempotent.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Dense but front-loaded: the core action and side effect come first, parameter notes second, follow-up workflow last. Every sentence adds information, though the single-paragraph packing with inline code makes it slightly less scannable than it could be.

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 5-parameter mutation with a nested config object and no annotations, the description covers the distinctive behavior, parameter intent, and next steps, and an output schema already documents the return. Permission requirements and failure semantics are the remaining gaps.

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 0%, so the description must compensate, and it does for the non-obvious parameters: `config` is tied to list_connectors/discover_source, `poll` is scoped to pull connectors, and `project` has a default plus a note that other projects can use it. `name` and `connector` are left implicit, and no format examples (poll syntax) are given.

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 ('Create a data source') plus a distinctive side effect ('starts ingesting it immediately (no restart)'). It also names the relevant siblings (list_connectors, discover_source, list_sources, catalog_describe) so an agent can place it in a workflow.

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?

Gives clear when-to-use context and prescribes a follow-up sequence (list_sources to watch ingestion, catalog_describe to inspect labels) and points to list_connectors/discover_source for building config. It lacks explicit when-not-to-use guidance or preconditions (e.g., permissions), so it stops short of a 5.

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