Skip to main content
Glama
itential

Itential MCP Server

Official
by itential

Get Task Metrics for Workflow

get_task_metrics_for_workflow
Read-onlyIdempotent

Retrieve task execution metrics for a named workflow to analyze individual task performance and pinpoint optimization opportunities.

Instructions

Get all task metrics for the specified workflow from Workflow Engine.

Retrieves task execution metrics filtered by a specific workflow name, providing detailed insights into the performance of individual tasks within that particular workflow for targeted analysis and optimization.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesThe name of the workflow to retrieve task metrics for

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYesResponse model for task metrics collection endpoints. This Pydantic RootModel provides a standardized response format for API endpoints that return collections of task-level metrics from the Itential Platform workflow engine. It wraps a list of TaskMetricElement objects, enabling type-safe handling of task performance data across automation workflows. The root model pattern allows the response to be treated as a list while maintaining proper validation and serialization capabilities for the contained task metric elements, supporting comprehensive workflow monitoring and analysis. Args: root: List of TaskMetricElement objects containing task performance data. Defaults to an empty list if not provided. Attributes: root (List[TaskMetricElement]): Collection of task metric elements with application usage patterns and execution statistics for workflow analysis Example: Creating a response with multiple task metrics: >>> task1 = TaskMetricElement(taskType="automatic", name="validate-config", ... metrics=[], app="validator") >>> task2 = TaskMetricElement(taskType="manual", name="approve-deploy", ... metrics=[], app="approval-service") >>> response = GetTaskMetricsResponse([task1, task2]) >>> print(len(response.root)) # 2 >>> print(response.root[0].task_type) # "automatic" >>> print(response.root[1].name) # "approve-deploy" Notes: - Uses default_factory=list to create empty collections when needed - Supports iteration and indexing through the root attribute - Maintains type safety for all contained TaskMetricElement objects - Enables filtering and analysis of tasks by application, workflow, or type
Behavior3/5

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

Annotations already declare readOnlyHint and idempotentHint, so the safety profile is covered. The description adds that it retrieves execution metrics and provides performance insights, but does not disclose additional behavioral details such as pagination, error handling, or empty result behavior.

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 two sentences, front-loaded with the core action, and contains no unnecessary repetition or filler. The second sentence adds context about the purpose of the metrics without overstating.

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 the tool's simplicity (one parameter), strong annotations, and existing output schema, the description is largely complete. It could be enhanced by mentioning that it focuses on workflow-level metrics as opposed to app- or task-level metrics, but overall it provides enough context for correct invocation.

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%, with the parameter 'name' adequately described in the schema. The description reinforces that it filters by workflow name but adds no extra meaning beyond the schema, such as format, case sensitivity, or defaults.

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 clearly states the tool retrieves all task metrics for a specified workflow, using a specific verb and resource. It distinguishes itself by the workflow name scope, but does not explicitly contrast with closely related siblings like get_task_metrics, get_task_metrics_for_app, or get_task_metrics_for_task.

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?

The description implies usage for workflow-specific task metrics but provides no explicit guidance on when to choose this tool over alternatives, nor any exclusions. Given the many sibling metric tools, this is a notable gap.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/itential/itential-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server