Skip to main content
Glama

FlowCastle

by ai.flowcastle
OverviewDiscussionsAdmin

query_flow_logs

Read-only

Read the bot execution log (flow_execution_log) — the record of what the runtime actually did, and the only place that separates "the action ran" from "the action produced output". Read-only; requires the view_logs permission. Two modes: without groupBy it returns the newest matching rows, with groupBy it returns a grouped rollup ("what is failing right now") — group by error for distinct failures, action for which step, flow for where, day for whether it is new, then re-run with the same filters and no groupBy to read the rows behind a group. The window is always bounded: it defaults to the last 24 hours and cannot exceed 30 days. For one contact's history, get_contact_activity with includeFlowRuns is the narrower read.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
botIdNoOnly this bot's rows. Omit for every bot in the application.
levelNoOnly rows at this level. `ERROR` is the usual starting point.
limitNoRows (max 200, default 50) or groups (max 100, default 25) to return.
actionNoExact action name, as it appears in the `action` field of a returned row.
flowIdNoOnly rows produced while running this flow.
searchNoSubstring match on the message or the error message.
blockIdNoOnly rows produced by this block.
endDateNoEnd of the window, ISO 8601. Defaults to now.
groupByNoReturn a rollup grouped by this dimension instead of raw rows.
contactIdNoOnly rows for this contact — one person's trace through the bot.
startDateNoStart of the window, ISO 8601. Defaults to 24 hours before endDate.
applicationIdNoApplication (workspace) id. Optional: an application-scoped key (app_...) defaults to its own application, but a personal key (usr_...) has no default and omitting it fails with MCP_APPLICATION_REQUIRED. Call list_applications to get the id.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / level / enum
      Previous value: -[
-  "INFO",
-  "WARNING",
-  "ERROR",
-  "DEBUG"
-]New value: +[
+  "INFO",
+  "WARNING",
+  "ERROR"
+]
  2. Added

TDQS

A4.8/5.0
Behavior5/5

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

Annotations only declare readOnlyHint and openWorldHint; the description goes further by disclosing the required view_logs permission, the groupBy mode split and its row/group semantics, and the bounded window (default 24h, max 30 days). These are behavioral facts not present in the 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?

Front-loaded with the resource identity and safety, then modes, then constraints, then the alternative — a logical order with little waste. It is dense and long, but each sentence carries distinct operational value for a 12-parameter tool, so the length is justified rather than padded.

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 12-param, zero-required read tool with no output schema, the description supplies what the structured fields cannot: the mode model, the window bounds, auth requirement, and the sibling alternative. An agent has enough to select and invoke it correctly without opening the schema.

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 description coverage is 100%, so the baseline is 3. The description nonetheless adds meaning beyond the schema by explaining what groupBy values signify (error=distinct failures, action=which step, flow=where, day=whether new) and how mode selection changes output shape, which the schema does not convey.

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 (read the bot execution log / flow_execution_log) and adds a discriminating qualifier: it is the only place separating 'the action ran' from 'the action produced output'. It also explicitly names the narrower sibling read (get_contact_activity with includeFlowRuns), so an agent can route between them.

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?

Gives explicit when-to-use guidance for the two modes: without groupBy returns newest rows, with groupBy returns a rollup for 'what is failing right now'. It even recommends a concrete dimension mapping (error, action, flow, day) and prescribes the follow-up workflow (re-run with same filters and no groupBy). Alternative for a single contact is named with its condition.

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

All FlowCastle 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