Skip to main content
Glama
railsware

Coupler Analytics

by railsware

list-dataflows

Idempotent

Retrieve a list of your Coupler.io data flows and find the UUID of any flow by its name.

Instructions

List my Coupler.io data flows. Use this to get the ID (uuid format) of a data flow by its name.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
dataflowsYes

Implementation Reference

  • The handler function that executes the 'list-dataflows' tool. It creates a CouplerioClient, queries dataflows with type=from_template, and returns the result as JSON.
    export const handler = async (): Promise<CallToolResult> => {
      const coupler = new CouplerioClient({ auth: COUPLER_ACCESS_TOKEN })
      const query = new URLSearchParams({ type: 'from_template' })
    
      const response = await coupler.request(`/dataflows?${query}{?type}`)
    
      if (!response.ok) {
        const errorText = await buildErrorMessage({ response, customText: 'Failed to list data flows.'})
    
        logger.error(errorText)
        return textResponse({
          isError: true,
          text: errorText
        })
      }
    
      const dataflows = await response.json()
    
      return textResponse({ text: JSON.stringify(dataflows, null, 2), structuredContent: { dataflows } })
    }
  • Input and output schema definitions. Input is an empty strict object. Output describes an array of dataflows with id, name, last_successful_execution_id, and last_success_run_at fields.
    import z from 'zod'
    import { zodToJsonSchema } from 'zod-to-json-schema'
    
    export const inputSchema = zodToJsonSchema(z.object({}).strict())
    
    const zodOutputSchema = z.object({
      dataflows: z.array(
        z.object({
          id: z.string().describe('The ID of the dataflow.'),
          name: z.string().describe('The name of the dataflow.'),
          last_successful_execution_id: z.string().nullish().describe('The ID of the last successful run (execution) of the dataflow.'),
          last_success_run_at: z.string().nullish().describe('The date and time of the last successful run (execution) of the dataflow. ISO 8601 format.'),
        })
      )
    })
    
    export const outputSchema = zodToJsonSchema(zodOutputSchema)
  • Registration in the ListToolsRequestSchema handler that exposes the tool via MCP's list tools capability.
    server.setRequestHandler(
      ListToolsRequestSchema,
      async () => ({
        tools: [
          getData.toolListEntry,
          getSchema.toolListEntry,
          listDataflows.toolListEntry,
          getDataflow.toolListEntry,
        ]
      })
    )
  • Registration in the TOOL_MAP that maps the tool name 'list-dataflows' to its handler for invocation via CallToolRequestSchema.
    const TOOL_MAP = {
      [getData.name]: getData.handler,
      [getSchema.name]: getSchema.handler,
      [listDataflows.name]: listDataflows.handler,
      [getDataflow.name]: getDataflow.handler,
    }
  • The index file that re-exports handler, defines name, description, annotations, and composes the toolListEntry for registration.
    import { inputSchema, outputSchema } from './schema.js'
    
    export { handler } from './handler.js'
    export const name = 'list-dataflows'
    export const description = 'List my Coupler.io data flows. Use this to get the ID (uuid format) of a data flow by its name.'
    
    const annotations = {
      title: 'List Coupler.io data flows.',
      idempotentHint: true,
    }
    
    export const toolListEntry = {
      name,
      description,
      inputSchema,
      outputSchema,
      annotations,
    }
Behavior4/5

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

Annotations include idempotentHint=true, indicating no side effects. Description adds that it lists 'my' data flows (scope) and returns IDs, which is consistent and adds value.

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 short, informative sentences with no extraneous information. Purpose and specific usage are front-loaded.

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

Completeness5/5

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

For a parameterless list tool with an output schema, the description covers the essential: it lists flows and can be used to find an ID by name. No further guidance is needed.

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?

Tool has zero parameters, baseline is 4. Description does not add parameter info, but schema coverage is 100% since there are no parameters.

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?

Clearly states it lists Coupler.io data flows and specifies the use case: to get a data flow's UUID by name. Distinguishes from sibling tools like get-dataflow (which likely returns a single flow) by its listing nature.

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?

Explicitly advises using it to retrieve a data flow ID by name, providing a clear context. Does not mention when not to use or alternatives, but for a simple list tool this is sufficient.

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/railsware/coupler-io-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server