Skip to main content
Glama

Valuein — SEC EDGAR Fundamentals & Smart-Money Data

by io.github.valuein
OverviewDiscussionsAdmin

Run Saved Workflow

run_workflow
Read-onlyIdempotent

Resolve a saved workflow by id and return a structured execution plan for a single ticker. Each plan entry names a real MCP tool or SOP plus its ticker-substituted arguments; the calling agent invokes them in order, applying any skip_if predicate against the previous step's output.

This tool does NOT execute the steps server-side. It plans; the agent runs. Iterate through plan[] in order, call the named tool/SOP with args, accumulate outputs, and apply each step's skip_if (skip the step when the previous output's path equals equals).

Workflows are private state owned by the calling user. Sample-tier callers are rejected. Pair with list_workflows (frontend) to discover available workflow_ids.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tickerNoUS-listed ticker the workflow should run against, e.g. 'AAPL'. Pass either `ticker` (single) or `tickers` (batch up to 50). Exactly one is required.
tickersNoBatch mode — array of US-listed tickers, up to 50. When provided, the response has `plans[]` (one plan per ticker) instead of `plan`. Parity with the frontend batch-runner so agents can request 'plan over my watchlist' in a single call.
workflow_idYesWorkflow id returned by the frontend workflow builder.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
metaYesProvenance envelope — data lineage for every MCP response
planYes
plansYes
tickerYes
workflowYes
instructionsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / properties / meta / properties / fundamentals_as_of / description
      Previous value: -"ISO timestamp when the FINANCIAL STATEMENTS were last rebuilt. Use THIS — not `last_updated` — when telling a user how current the fundamentals are. The snapshot is republished on every weekday price refresh while the statements are carried forward unchanged, so `last_updated` can be far more recent than the numbers it sits next to."New value: +"ISO timestamp when the FINANCIAL STATEMENTS were last rebuilt in bulk. Use THIS — not `last_updated` — when telling a user how current the cross-sectional fundamentals are. The snapshot is republished on every weekday price refresh while the statements are carried forward unchanged, so `last_updated` can be far more recent than the numbers it sits next to. It is a floor for a single filer, not a ceiling: a filer with a live partition receives its filing, facts and ratios intraday (minutes after EDGAR dissemination), so an entity-scoped read may carry a filing newer than this; cross-sectional ranks (factor scores, earnings signals) refresh with the weekly bulk export."
  2. Changed2 schema fields changed
    • addedOutput schema / properties / meta / properties / fundamentals_as_of
      Added value: +{
+  "description": "ISO timestamp when the FINANCIAL STATEMENTS were last rebuilt. Use THIS — not `last_updated` — when telling a user how current the fundamentals are. The snapshot is republished on every weekday price refresh while the statements are carried forward unchanged, so `last_updated` can be far more recent than the numbers it sits next to.",
+  "type": "string"
+}
    • addedOutput schema / properties / meta / properties / price_as_of
      Added value: +{
+  "description": "ISO timestamp when the price surfaces were last refreshed.",
+  "type": "string"
+}
  3. Changed2 schema fields changed
    • addedOutput schema / properties / meta / properties / cost_usd
      Added value: +{
+  "additionalProperties": false,
+  "description": "Per-call cost transparency. Omitted for subscription-only tools that have no PAYG-equivalent price.",
+  "properties": {
+    "amount_usd": {
+      "minimum": 0,
+      "type": "number"
+    },
+    "basis": {
+      "description": "payg_charge = real agent-pay charge. payg_rate_card = indicative price, not billed.",
+      "enum": [
+        "payg_charge",
+        "payg_rate_card"
+      ],
+      "type": "string"
+    },
+    "billed": {
+      "description": "true = this amount was actually charged via PAYG for this call. false = indicative PAYG-equivalent value; your plan already covers this call for free.",
+      "type": "boolean"
+    }
+  },
+  "required": [
+    "amount_usd",
+    "billed",
+    "basis"
+  ],
+  "type": "object"
+}
    • addedOutput schema / properties / meta / properties / latency_ms
      Added value: +{
+  "description": "Wall-clock milliseconds this tool call took, measured server-side around the handler.",
+  "minimum": 0,
+  "type": "integer"
+}
  4. Changed1 schema field changed
    • addedOutput schema / properties / meta / properties / pit_safe / description
      Added value: +"true iff a zero-look-ahead point-in-time cut was applied to every returned figure"
  5. Changed9 schema fields changed
    • changedInput schema / properties / ticker / description
      Previous value: -"US-listed ticker the workflow should run against, e.g. 'AAPL'."New value: +"US-listed ticker the workflow should run against, e.g. 'AAPL'. Pass either `ticker` (single) or `tickers` (batch up to 50). Exactly one is required."
    • addedInput schema / properties / tickers
      Added value: +{
+  "description": "Batch mode — array of US-listed tickers, up to 50. When provided, the response has `plans[]` (one plan per ticker) instead of `plan`. Parity with the frontend batch-runner so agents can request 'plan over my watchlist' in a single call.",
+  "items": {
+    "maxLength": 10,
+    "minLength": 1,
+    "type": "string"
+  },
+  "maxItems": 50,
+  "minItems": 1,
+  "type": "array"
+}
    • changedInput schema / required
      Previous value: -[
-  "workflow_id",
-  "ticker"
-]New value: +[
+  "workflow_id"
+]
    • addedOutput schema / properties / plan / anyOf
      Added value: +[
+  {
+    "items": {
+      "additionalProperties": false,
+      "properties": {
+        "args": {
+          "additionalProperties": {},
+          "type": "object"
+        },
+        "kind": {
+          "enum": [
+            "tool",
+            "sop"
+          ],
+          "type": "string"
+        },
+        "label": {
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "name": {
+          "type": "string"
+        },
+        "position": {
+          "type": "integer"
+        },
+        "skip_if": {
+          "anyOf": [
+            {
+              "additionalProperties": false,
+              "properties": {
+                "equals": {
+                  "type": "string"
+                },
+                "path": {
+                  "type": "string"
+                }
+              },
+              "required": [
+                "path",
+                "equals"
+              ],
+              "type": "object"
+            },
+            {
+              "type": "null"
+            }
+          ]
+        },
+        "step_id": {
+          "type": "string"
+        }
+      },
+      "required": [
+        "step_id",
+        "position",
+        "kind",
+        "name",
+        "label",
+        "args",
+        "skip_if"
+      ],
+      "type": "object"
+    },
+    "type": "array"
+  },
+  {
+    "type": "null"
+  }
+]
    • removedOutput schema / properties / plan / items
      Removed value: -{
-  "additionalProperties": false,
-  "properties": {
-    "args": {
-      "additionalProperties": {},
-      "type": "object"
-    },
-    "kind": {
-      "enum": [
-        "tool",
-        "sop"
-      ],
-      "type": "string"
-    },
-    "label": {
-      "type": [
-        "string",
-        "null"
-      ]
-    },
-    "name": {
-      "type": "string"
-    },
-    "position": {
-      "type": "integer"
-    },
-    "skip_if": {
-      "anyOf": [
-        {
-          "additionalProperties": false,
-          "properties": {
-            "equals": {
-              "type": "string"
-            },
-            "path": {
-              "type": "string"
-            }
-          },
-          "required": [
-            "path",
-            "equals"
-          ],
-          "type": "object"
-        },
-        {
-          "type": "null"
-        }
-      ]
-    },
-    "step_id": {
-      "type": "string"
-    }
-  },
-  "required": [
-    "step_id",
-    "position",
-    "kind",
-    "name",
-    "label",
-    "args",
-    "skip_if"
-  ],
-  "type": "object"
-}
    • removedOutput schema / properties / plan / type
      Removed value: -"array"
    • addedOutput schema / properties / plans
      Added value: +{
+  "anyOf": [
+    {
+      "items": {
+        "additionalProperties": false,
+        "properties": {
+          "plan": {
+            "items": {
+              "$ref": "#/properties/plan/anyOf/0/items"
+            },
+            "type": "array"
+          },
+          "ticker": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "ticker",
+          "plan"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    {
+      "type": "null"
+    }
+  ]
+}
    • changedOutput schema / properties / ticker / type
      Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
    • changedOutput schema / required
      Previous value: -[
-  "meta",
-  "workflow",
-  "ticker",
-  "plan",
-  "instructions"
-]New value: +[
+  "meta",
+  "workflow",
+  "ticker",
+  "plan",
+  "plans",
+  "instructions"
+]
  6. Added

TDQS

A4.3/5.0
Behavior5/5

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

Beyond the readOnly/idempotent annotations, the description discloses that the tool plans but does not execute, that workflows are private per-user, and that sample-tier callers are rejected. It also defines the `skip_if` evaluation semantics, which is valuable behavioral context not present in annotations.

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?

The description is dense but well structured, with the core purpose and the critical non-execution caveat front-loaded. Some redundancy exists between 'does NOT execute the steps server-side' and 'It plans; the agent runs,' which adds a bit of length, but the overall organization is logical and readable.

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 description covers the tool's purpose, execution loop, limitations, and pairing, and an output schema exists. The main gap is that the prose is written almost entirely for the single-ticker `plan` case and never acknowledges the batch `tickers`/`plans[]` mode, which the schema documents but the description should reinforce given the misleading 'single ticker' opening.

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 coverage is 100%, and the parameter descriptions already explain ticker/tickers mutual exclusivity, the 50-ticker limit, and the `plans[]` batch response. The description adds no new input-parameter semantics and even omits batch mode from its main prose, so it stays at the schema-driven baseline.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific action ('Resolve a saved workflow by id') and a clear deliverable (a structured execution plan), and it distinguishes itself from execution tools by noting the agent is the executor. However, the opening 'for a single ticker' is not fully accurate because the schema supports batch `tickers` up to 50, and the body never reconciles this with `plans[]`.

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?

The description gives explicit operational instructions: iterate through `plan[]`, call each named tool/SOP with `args`, accumulate outputs, and apply `skip_if` predicates. It also states a hard exclusion ('This tool does NOT execute the steps server-side'), a caller restriction (sample-tier rejected), and pairs with `list_workflows` for discovery.

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

All Valuein — SEC EDGAR Fundamentals & Smart-Money Data toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources