Skip to main content
Glama
Rootly MCP server

Rootly MCP server

Official
by rootlyhq

Get Workflow Task Params Schema

get_workflow_task_params_schema
Read-onlyIdempotent

Fetch the task_params field schema for a workflow task type to know which fields to include when creating or updating a workflow task.

Instructions

Get the task_params fields for one workflow task type.

Call this before create_workflow_task or update_workflow_task: their task_params schema lists only the task types, not each type's fields. Pass the result's fields inside data.attributes.task_params, together with task_type.

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": {
      "task_type": "<task_type>"
    },
    "name": "get_workflow_task_params_schema"
  }
}

Input Schema

NameRequiredDescriptionDefault
task_typeYesWorkflow task type, e.g. 'send_slack_message' or 'create_jira_issue'. The task_type enum on create_workflow_task lists every value.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv3.0.0

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=false and destructiveHint=false, so the safety profile is covered. The description adds genuinely new behavioral context: it is a per-type lookup (one task type per call) and its output is meant to be fed into a different tool's payload rather than acted on directly. It does not say what happens for an unrecognized task_type, which is the only remaining gap.

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?

Three short sentences: what it does, when to call it and why, then how to apply the result. The action-oriented instruction is front-loaded and there is no filler or restatement of the title.

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 single-parameter lookup tool with an output schema and full annotation coverage, the description supplies everything an agent needs: purpose, prerequisite ordering versus the two mutation siblings, and how to consume the return value. Return-value structure is correctly left to the output 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 coverage is 100%, so task_type is already documented with examples and the pointer to the enum on create_workflow_task. The description still adds meaning beyond the schema by establishing the one-type-per-call granularity and the requirement to pair the returned fields with task_type inside data.attributes.task_params.

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 first sentence names a specific resource (task_params fields) scoped to one workflow task type, which is a distinct operation from the sibling get_workflow_task or list_workflow_tasks. An agent can tell exactly what it gets back without opening the schema.

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?

It states the precise trigger ('Call this before create_workflow_task or update_workflow_task') and the reason those siblings are insufficient ('their task_params schema lists only the task types, not each type's fields'). It also closes the loop by telling the agent where to put the result, so there is no ambiguity about sequencing or downstream use.

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