Skip to main content
Glama

ToolForte

by com.toolforte
OverviewDiscussionsAdmin

List saved workflows

workflow_list
Read-onlyIdempotent

List the workflows saved to the ToolForte account this API key belongs to. A workflow runs several ToolForte tools in order, passing each one the output of an earlier step, so it does a whole job in one call instead of you orchestrating the steps yourself. Returns each workflow's id, the inputs it expects, the steps it runs and what a run costs. Call this first: workflow_run needs an id from here. Requires an API key, because a workflow belongs to an account. Get a key in one request with POST https://toolforte.com/api/v1/keys/bootstrap and {"email":"you@example.com"}, which emails it to that address, or create one at https://toolforte.com/developers, and send it on the MCP connection as the header Authorization: Bearer tf_...

Input Schema

NameRequiredDescriptionDefault
limitNoHow many to return, newest first.

Output Schema

NameRequiredDescriptionDefault
countNoNumber of items
resultNoThe result, when it is not an object
workflowsNoThe workflows on the account

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • removedInput schema / $schema
      Removed value: -"https://json-schema.org/draft/2020-12/schema"
    • removedOutput schema / $schema
      Removed value: -"https://json-schema.org/draft/2020-12/schema"
  2. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "additionalProperties": {},
+  "properties": {
+    "count": {
+      "description": "Number of items",
+      "type": "number"
+    },
+    "result": {
+      "description": "The result, when it is not an object"
+    },
+    "workflows": {
+      "description": "The workflows on the account",
+      "items": {},
+      "type": "array"
+    }
+  },
+  "type": "object"
+}
  3. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -{
-  "$schema": "https://json-schema.org/draft/2020-12/schema",
-  "additionalProperties": {},
-  "properties": {
-    "count": {
-      "description": "Number of items",
-      "type": "number"
-    },
-    "result": {
-      "description": "The result, when it is not an object"
-    },
-    "workflows": {
-      "description": "The workflows on the account",
-      "items": {},
-      "type": "array"
-    }
-  },
-  "type": "object"
-}New value: +null
  4. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "additionalProperties": {},
+  "properties": {
+    "count": {
+      "description": "Number of items",
+      "type": "number"
+    },
+    "result": {
+      "description": "The result, when it is not an object"
+    },
+    "workflows": {
+      "description": "The workflows on the account",
+      "items": {},
+      "type": "array"
+    }
+  },
+  "type": "object"
+}
  5. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so safety is covered. The description adds genuinely useful non-schema context: the API key requirement, why it's required (account ownership), and how to obtain a key. It does not disclose pagination behavior or rate limits, keeping 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.

Conciseness4/5

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

Purpose and the 'call this first' directive are front-loaded and tight. The closing bootstrap/auth paragraph is longer than strictly necessary for a read-only list call, though it is at least actionable rather than filler.

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?

An output schema exists, so return shape needn't be explained, yet the description still summarizes the key fields (id, inputs, steps, cost). With auth prerequisites, sequencing, and scope all covered, an agent has everything needed to call it correctly.

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% and the single 'limit' parameter already documents its range and 'newest first' ordering. The description adds nothing about the parameter, so the baseline 3 applies.

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+resource+scope: 'List the workflows saved to the ToolForte account this API key belongs to.' It also explains what a workflow actually is (ordered tool steps, output chaining), which lets an agent distinguish it from workflow_run without opening schemas.

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

Usage Guidelines5/5

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

Explicit sequencing instruction: 'Call this first: workflow_run needs an id from here.' That names the alternative and the condition that selects it, front-loaded before the auth details.

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

All ToolForte toolsInspect
Try in Browser
Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources