Skip to main content
Glama

Read a workflow's collected data

writ_workflow_data
Read-onlyIdempotent

Reads a saved workflow's collected data as a table: q filters, run_id picks one run, refs returns full records.

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": "writ_workflow_data"
  }
}

Input Schema

NameRequiredDescriptionDefault
qNo
refsNoFull records by '<run_id>:<record_index>'.
viewNo
limitNo
deviceNo
outputNo
run_idNo
workflowNo
workflow_idNo
preview_charsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changed
    • addedInput schema / properties / device
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / output
      Added value: +{
      +  "type": "object"
      +}
    • addedInput schema / properties / preview_chars
      Added value: +{
      +  "type": "integer"
      +}
    • addedInput schema / properties / view
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / workflow
      Added value: +{
      +  "type": "string"
      +}
  2. Changed7 schema fields changed
    • removedInput schema / properties / device
      Removed value: -{
      -  "description": "A linked Writ desktop's agent_id (writ_devices) to act on. Omitted: the desktop this connection chose with writ_devices action='use', if any.",
      -  "type": "string"
      -}
    • removedInput schema / properties / output
      Removed value: -{
      -  "description": "Response shape, for an answer a program or an API consumes rather than a reader. {shape: 'envelope' (default: Writ's full answer, projected) | 'table' ({columns, rows, total}) | 'records' (bare list of records) | 'record' (the newest record alone: one entity, a usage meter, a dashboard), fields: ['used', 'percent_used as pct', 'items.0.price as first_price'] (ordered pick, renames, dotted paths; a missing path is null, so keys are stable), exclude: ['depth'], include_meta: false (page metadata content_kind/depth/thumbnails is stripped unless true), key: 'usage' (wrap)}. On writ_crawl_site with save_as it is saved as the API's default shape.",
      -  "properties": {
      -    "exclude": {
      -      "items": {
      -        "type": "string"
      -      },
      -      "type": "array"
      -    },
      -    "fields": {
      -      "items": {
      -        "type": "string"
      -      },
      -      "type": "array"
      -    },
      -    "include_meta": {
      -      "type": "boolean"
      -    },
      -    "key": {
      -      "type": "string"
      -    },
      -    "shape": {
      -      "enum": [
      -        "envelope",
      -        "table",
      -        "records",
      -        "record"
      -      ],
      -      "type": "string"
      -    }
      -  },
      -  "type": "object"
      -}
    • removedInput schema / properties / preview_chars
      Removed value: -{
      -  "description": "Cut string cells to this many characters (default 2000; 0 = full cells).",
      -  "type": "integer"
      -}
    • removedInput schema / properties / q / description
      Removed value: -"Substring filter across fields."
    • changedInput schema / properties / refs / description
      Previous value: -"Hydration: full untruncated records by ref '<run_id>:<record_index>' (both fields are on every row). Max 100."New value: +"Full records by '<run_id>:<record_index>'."
    • removedInput schema / properties / view
      Removed value: -{
      -  "description": "all | latest | run",
      -  "type": "string"
      -}
    • removedInput schema / properties / workflow
      Removed value: -{
      -  "type": "string"
      -}
  3. First observed

TDQS

C2.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and closed-world, so the safety profile is covered. The description adds genuinely new behavior ('as a table', 'refs returns full records', run scoping), but says nothing about pagination via limit, default row counts, or what happens when no run_id is supplied.

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?

One front-loaded sentence with no filler, and the parameter hints are compressed into a readable colon-delimited list. The density is high but nothing is wasted.

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

Completeness1/5

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

With 10 optional parameters, 10% schema coverage, no output schema, and a nested 'output' object, the description should carry most of the explanatory load but covers only a fraction. An agent cannot reliably choose workflow vs workflow_id, understand view/limit/output, or know what the table looks like.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 10% — only 'refs' is documented in the schema. The description explains three parameters (q, run_id, refs) and leaves view, limit, device, output, workflow, workflow_id, and preview_chars entirely unexplained in both places, which is a substantial gap for a 10-parameter tool.

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 gives a specific verb and resource ('Reads a saved workflow's collected data') plus the return shape ('as a table'), which is enough to distinguish it from export- or run-listing-oriented siblings. It stops short of naming any sibling it should be preferred over, so it is clear but not differentiating.

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

Usage Guidelines2/5

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

There is no statement of when to use this instead of writ_export_data, writ_workflow_runs, or writ_search_data, nor any prerequisites such as needing a prior run. The only guidance is embedded parameter hints ('q filters', 'run_id picks one run'), which is invocation help rather than tool selection guidance.

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.