Skip to main content
Glama
Teamwork

Teamwork

Official
by Teamwork
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Go
Remote

twprojects-get_workflow

Read-only

Retrieve a specific workflow by ID from Teamwork. Optionally select fields like name and defaultWorkflow to customize the response.

Instructions

Get workflow.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesThe ID of the workflow to get.
fieldsNoThe attributes to return for each workflow, from the listed names.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
workflowNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv1.39.3
    • removedInput schema / properties / fields / anyOf
      Removed value: -[
-  {
-    "items": {
-      "enum": [
-        "id",
-        "name",
-        "defaultWorkflow"
-      ],
-      "type": "string"
-    },
-    "type": "array"
-  },
-  {
-    "type": "null"
-  }
-]
    • addedInput schema / properties / fields / items
      Added value: +{
+  "enum": [
+    "id",
+    "name",
+    "defaultWorkflow"
+  ],
+  "type": "string"
+}
    • addedInput schema / properties / fields / type
      Added value: +"array"
  2. Changed5 schema fields changedv1.27.2
    • addedInput schema / properties / fields
      Added value: +{
+  "anyOf": [
+    {
+      "items": {
+        "enum": [
+          "id",
+          "name",
+          "defaultWorkflow"
+        ],
+        "type": "string"
+      },
+      "type": "array"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "description": "The attributes to return for each workflow, from the listed names."
+}
    • removedOutput schema / additionalProperties
      Removed value: -false
    • removedOutput schema / properties / workflow / additionalProperties
      Removed value: -false
    • removedOutput schema / properties / workflow / required
      Removed value: -[
-  "id",
-  "name",
-  "defaultWorkflow"
-]
    • removedOutput schema / required
      Removed value: -[
-  "workflow"
-]
  3. Addedv1.26.0
  4. Removedv1.25.0
  5. Addedv1.18.3
  6. Removedv1.18.2
  7. Addedv1.17.2

TDQS

C2.3/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false; the description adds no behavioral detail beyond the word 'get'. It doesn't mention field selection behavior, default returned attributes, or anything about the operation's effects or requirements.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is short but under-specified rather than effectively concise. A two-word sentence that simply repeats the tool name does not earn its place and leaves all useful context to the schema.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The operation is a simple get-by-id with a complete input schema and an output schema, so an agent can technically call it. However, the description provides no resource context or relationship to sibling workflow tools, leaving clear semantic gaps.

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 description coverage is 100%: both id and fields have descriptions, and fields has an enum. The description itself adds no parameter meaning, so the baseline of 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description is literally 'Get workflow.', which restates the tool name and title without adding any detail. It identifies a verb and resource, but says nothing about what a workflow is, that it is fetched by ID, or how it differs from list_workflows or get_workflow_stage.

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?

No when-to-use guidance is provided: it does not say to use this when a workflow ID is known, nor does it point to list_workflows for fetching all workflows. The agent must infer usage entirely from the tool name and schema.

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