Skip to main content
Glama

Pin a workflow as a tool

writ_pin_workflow_tool
Idempotent

Pins (or unpins) a saved workflow as its own run_ tool on this server.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "writ_pin_workflow_tool"
  }
}

Input Schema

NameRequiredDescriptionDefault
pinnedNo
workflowNo
workflow_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / workflow
      Added value: +{
      +  "type": "string"
      +}
  2. Changed2 schema fields changed
    • removedInput schema / properties / pinned / description
      Removed value: -"true (default) pins; false unpins."
    • removedInput schema / properties / workflow
      Removed value: -{
      -  "description": "Workflow name (or workflow_id).",
      -  "type": "string"
      -}
  3. First observed

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, idempotentHint=true and destructiveHint=false, so the safety profile is covered. The description adds the meaningful side effect (a new run_<name> tool appears on the server), but says nothing about permissions, what happens on name collisions, or whether unpinning removes the tool.

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

Conciseness4/5

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

A single front-loaded sentence with no filler, and the effect on the server is stated up front. It is efficient but arguably too terse given the parameter ambiguity it leaves behind.

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

Completeness2/5

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

For a mutation tool with no output schema and zero parameter documentation, the description is thin: it does not explain the workflow/workflow_id choice, the default when pinned is omitted, or what the caller gets back. An agent could easily call it with the wrong identifier field.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% across three parameters, so the description must carry the load and largely does not. 'Pins (or unpins)' hints at the boolean, and 'saved workflow' hints at the workflow field, but the critical ambiguity between workflow (string) and workflow_id (integer) is never resolved, nor is which is required.

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 gives a specific verb pair (pins/unpins) and a concrete resource (a saved workflow), plus the observable effect: it becomes its own run_<name> tool on this server. That distinguishes it from writ_run_workflow and writ_list_workflows, though it never names a sibling explicitly.

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?

There is no guidance on when to pin versus when to simply run a workflow, no prerequisites, and no mention of how to reverse the operation beyond the parenthetical 'unpins'. The agent must infer that pinned=false is the unpin path.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.