Skip to main content
Glama

List Reverse Etl Processes Tool

list-reverse-etl-processes
Read-onlyIdempotent

List reverse ETL processes the current user can see. Requires data-distribution permission. Returns a short summary with preset_type and no SQL, delivery configuration, or destination settings.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list-reverse-etl-processes"
  }
}

Input Schema

NameRequiredDescriptionDefault
spaceNoSpace slug. Required when the token is bound to more than one space. Omit it when the token has one space.
project_idNoOptional project id. When omitted, processes from every permitted project are returned.

Output Schema

NameRequiredDescriptionDefault
processesYes
permission_noticeYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already establish read-only and idempotent behavior, so the description does not need to repeat safety characteristics. It adds meaningful behavioral detail by disclosing the permission requirement and clarifying that results are a short summary containing preset_type but omitting SQL, delivery configuration, and destination settings.

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 three short sentences with no filler. It is front-loaded with the core purpose, then adds permission and response-shape context in a logical order.

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?

The tool has an output schema, full parameter schema coverage, and clear annotations, so the description does not need to explain every return field. It is nearly complete for this complexity level, though it could mention pagination or result limits if relevant.

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 explains both the space and project_id parameters in detail. The description does not add further meaning about these parameters, which is acceptable because the schema carries that burden.

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 uses a specific verb and resource: 'List reverse ETL processes.' It also scopes the result to what 'the current user can see,' which clearly distinguishes this collection-listing tool from the singular sibling get-reverse-etl-process.

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?

The description states a prerequisite ('Requires data-distribution permission'), which gives useful context for when the call will work. However, it does not explicitly compare this tool to get-reverse-etl-process or explain when an agent should prefer one over the other.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources