Skip to main content
Glama

get_workflow_rules

Read-onlyIdempotent

Retrieve a project's workflow rules, including allowed transitions, policies, and agent permissions. Check before moving tasks to confirm restrictions and avoid invalid state changes.

Instructions

Get workflow rules for a project including allowed transitions, policies, and permissions for the calling agent. Read-only; check it before a move_task that may be restricted. get_assignment_rules covers routing; get_my_rules covers everything that binds you.

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": {
      "project_id": "<project_id>"
    },
    "name": "get_workflow_rules"
  }
}

Input Schema

NameRequiredDescriptionDefault
project_idYesProject UUID, from list_projects.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.1.6
    • changedInput schema / properties / project_id / description
      Previous value: -"Project ID."New value: +"Project UUID, from list_projects."
  2. First observedv0.1.1

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered; the description's 'Read-only' is largely redundant. It still adds useful behavioral context by stating that results include permissions for the calling agent and that this should be checked before a potentially restricted move_task.

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 with no wasted text. Purpose and contents are front-loaded, followed by the pre-move usage check and sibling differentiation.

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 one-parameter read-only getter with no output schema, the description is complete enough: it states what is returned, when to consult it, and how it differs from nearby tools. Annotations already cover the safety profile, so little else is needed.

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%, and the sole parameter project_id is already documented as coming from list_projects. The description adds no additional syntax or format details beyond what the schema provides, so the baseline of 3 is appropriate.

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 states a specific verb and resource - get workflow rules for a project - and names the concrete contents: allowed transitions, policies, and permissions for the calling agent. It also distinguishes itself from siblings by explicitly saying get_assignment_rules covers routing and get_my_rules covers everything that binds you.

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 gives an explicit usage condition: check this before a move_task that may be restricted. It also names the relevant alternative tools and their scopes, so an agent can choose between this, get_assignment_rules, and get_my_rules without guessing.

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