Skip to main content
Glama

Diagnose a workflow's HTTP lane

writ_diagnose_http_workflow
Read-onlyIdempotent

Explains why a saved workflow's run returned nothing or failed: HTTP-lane readiness and, with task_id, the run's requests and responses.

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_diagnose_http_workflow"
  }
}

Input Schema

NameRequiredDescriptionDefault
task_idNo
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 / task_id / description
      Removed value: -"Optional run to verify actual HTTP execution and output."
    • removedInput schema / properties / workflow
      Removed value: -{
      -  "type": "string"
      -}
  3. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered externally. The description usefully adds that the tool surfaces HTTP-lane readiness and per-task request/response detail, but says nothing about failure modes of the diagnosis itself or result shape.

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 dense sentence that front-loads the purpose and appends the conditional modifier after a colon; no filler words. Slightly compressed phrasing ('HTTP-lane readiness') costs a little clarity but nothing is wasted.

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?

For a read-only diagnostic with no output schema, describing the returned content conceptually is reasonable, and annotations carry the safety story. The gap is the all-optional, undescribed parameter set — an agent cannot tell from either schema or description whether to pass workflow, workflow_id, or both.

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, and the description only clarifies task_id ('with task_id, the run's requests and responses'). It never explains the difference between 'workflow' and 'workflow_id' or which one to supply, and since no parameters are required, an agent is left guessing how to identify the target workflow.

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 states a specific verb and target ('Explains why a saved workflow's run returned nothing or failed') and scopes the output to HTTP-lane readiness plus requests/responses when task_id is supplied. That is clear enough to distinguish a diagnostic tool from siblings like writ_run_workflow or writ_list_workflows, though it never names an alternative.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives an implied trigger — call this after a run returned nothing or failed — and notes the task_id conditional that changes what is returned. It stops short of when-not guidance or pointing to a related tool for other failure modes, so the agent must infer the boundary itself.

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.