Skip to main content
Glama

Analyze Newman failure

analyze_newman_failure
Read-only

Diagnoses Newman test failures and suggests corrected scripts or requests to resolve assertion, exception, or request errors.

Instructions

Diagnoses a failure and suggests a corrected script or request.

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": {
      "collectionSource": "<collectionSource>",
      "failure": "<failure>"
    },
    "name": "analyze_newman_failure"
  }
}

Input Schema

NameRequiredDescriptionDefault
failureYesA NewmanFailure item as returned by tool 4 or 5
collectionSourceYesExecuted collection (path, https URL, or Postman UID)

Output Schema

NameRequiredDescriptionDefault
llmYes
categoryYes
fixTargetYes
fixedExecYes
rootCauseYes
confidenceYes
suggestedFixYes
validationErrorNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

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, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds that the tool produces a suggested correction rather than applying one, which is genuinely useful and consistent with the read-only annotation. It says nothing about how the suggestion is derived, whether collectionSource is fetched over the network (relevant given openWorldHint), or what happens if the failure data is incomplete.

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 short sentence with zero filler, front-loading the action and the payoff. It is efficient but borders on under-specification for a tool whose inputs are non-obvious.

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?

An output schema exists, so return values needn't be explained, and both parameters are fully documented in the schema. What is missing is the operational context an agent needs to select this tool correctly — namely that it consumes a failure object produced by a prior run and that it only advises rather than mutates the collection.

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%, including nested fields for the failure object and the accepted forms of collectionSource, so the schema carries the parameter burden. The description adds no meaning beyond the schema — it does not clarify which failure types benefit most or how responseSnippet influences the diagnosis. Baseline 3 applies.

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?

States a specific verb and resource ("Diagnoses a failure") plus the outcome ("suggests a corrected script or request"), so the agent knows this is a remediation tool rather than a runner or reporter. It does not name any sibling or explain how it differs from run_newman_collection or generate_newman_report, leaving the agent to infer the relationship.

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 explicit when-to-use guidance, no prerequisites, and no mention of the alternative tools. The agent must infer that this is called after a Newman run fails and with a failure object from that run; nothing in the description says so.

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