Skip to main content
Glama
Sign In
Axonity Flow MCP Server

Axonity Flow MCP Server

Official
by AxonityAI
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

read_workflow_trigger_parameters

Retrieve input parameters required by workflow triggers to ensure correct invocation before starting a run.

Instructions

Read the input parameters a workflow's triggers expect — what a caller must supply to start it. Use this before authoring a webhook/cron/conditional trigger, or before start_workflow_run, so the trigger input matches. Read-only.

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": {
      "workflowId": "<workflowId>"
    },
    "name": "read_workflow_trigger_parameters"
  }
}

Input Schema

NameRequiredDescriptionDefault
workflowIdYesThe workflow's id.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

A4.6/5.0
Behavior4/5

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

States 'Read-only.', which is clear about safety given no annotations. Could add more about idempotence or side effects, but for a simple read with one parameter, it's sufficient.

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?

Two sentences, front-loaded purpose, no fluff. Every sentence earns its place.

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?

Given simplicity (1 param, no output schema), description covers purpose, usage, and read-only nature. Could be slightly more specific about the output (e.g., returns parameter names/types), but generally complete.

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 has one parameter with basic description. The description adds context that the output helps construct correct trigger inputs, enhancing meaning beyond the schema property description. Schema coverage is 100%.

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?

Description clearly states it reads input parameters for workflow triggers, using specific verb 'read' and resource 'workflow trigger parameters'. It distinguishes from siblings like start_workflow_run by indicating it's a preparatory step.

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?

Explicitly says 'Use this before authoring a webhook/cron/conditional trigger, or before start_workflow_run, so the trigger input matches.' This provides clear when-to-use guidance and implies when not to use (other contexts).

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