Skip to main content
Glama
Sign In
okraPDF PDF MCP server

okraPDF PDF MCP server

Official
by okracomputer
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

View Workflow

view_workflow
Read-only

Confirm and visualize a workflow as it is built. Finite definitions return validation and visualization; agent workflow scripts return parse/readiness state and plan estimate.

Instructions

Confirm a workflow as it is being built: finite definitions return visualization + validation, while agent workflow scripts return parse/readiness state and a best-effort plan estimate. Accepts a catalog name (e.g. staff.table-ingest) or a workflow id you authored.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "workflow_id": "<workflow_id>"
    },
    "name": "view_workflow"
  }
}

Input Schema

NameRequiredDescriptionDefault
workflow_idYesWorkflow id or catalog name to confirm/visualize (e.g. staff.table-ingest, or a wf_… you authored).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior4/5

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

The description goes beyond the readOnlyHint annotation by explaining the exact behavioral differences: finite definitions produce visualization+validation, while agent workflow scripts produce parse/readiness state and a best-effort plan estimate. This adds valuable insight into expected behavior without contradicting annotations.

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?

The description is extremely concise—two sentences—and front-loads the core purpose. Every clause adds value: purpose, type-specific behavior, and accepted input format. No wasteful repetition.

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?

For a single-parameter read-only tool with no output schema, the description sufficiently explains what the tool returns and under what conditions. It covers the key differentiators and usage context, making it complete enough for an agent to invoke 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?

The schema already provides a thorough description of parameter workflow_id, including examples. The description reinforces this by mentioning 'catalog name' and 'workflow id you authored,' but does not add substantially new meaning beyond the schema. Baseline 3 is appropriate given 100% schema coverage.

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?

The description clearly states the tool's action: 'Confirm a workflow as it is being built.' It also distinguishes between two workflow types and what each returns, which differentiates it from siblings like view_workflow_run or list_workflows.

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?

The phrase 'as it is being built' gives clear context for when to use this tool (during construction/validation of a workflow). It does not explicitly mention alternatives or exclusions, but the context implies it is not for viewing runs or listing workflows, which are covered by siblings.

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

Deploy Server

Other Tools