Skip to main content
Glama

Patch MCP

generate_test_scenario

Draft a new test scenario from the active agent context, or expand an existing description with realistic complications. New mode ignores description. Returns editable text without starting a call.

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": {
      "numberId": "<numberId>",
      "direction": "<direction>",
      "revision": "<revision>",
      "mode": "<mode>",
      "callMode": "<callMode>"
    },
    "name": "generate_test_scenario"
  }
}

Input Schema

NameRequiredDescriptionDefault
modeYes
callModeYesbot
numberIdYes
revisionYes
directionYes
descriptionNo
destinationNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.3/5.0
Behavior4/5

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

The annotations only declare the generic profile (readOnlyHint=false, destructiveHint=false, idempotentHint=false, openWorldHint=false), so the description carries real weight and delivers: the output is editable text rather than a launched test, no call is started, and the 'new' mode discards the description input. It still does not say whether a draft is persisted or what happens on repeated calls, so it stops short of full disclosure.

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?

Three short, front-loaded sentences with the primary action first and the two most decision-relevant facts (mode behavior, no call started) placed early. Slightly telegraphic phrasing ('New mode ignores description') costs a bit of readability but there is no filler.

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?

An output schema exists, so return values need not be described, but this is a 7-parameter, 5-required tool with three enums and zero schema documentation, and the description covers only one and a half of those parameters. For a tool that presumably operates within a specific test/agent context identified by numberId and revision, the definition leaves too much unstated.

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 7 parameters, so the description must compensate and largely does not. It only clarifies the 'description' parameter (ignored in new mode) and indirectly the 'mode' enum; numberId, revision, direction, callMode, and destination are left entirely unexplained in both schema and prose.

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 pairs a specific verb ('Draft') with a specific resource ('a new test scenario') and names two distinct modes (new vs. expand). It partially differentiates from siblings by noting it returns editable text 'without starting a call', which implicitly separates it from start_agent_test, though no sibling is explicitly named.

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 intra-tool guidance ('New mode ignores description', and expand mode adds complications to an existing description), which helps pick a mode. However, it never states when to reach for this tool rather than start_agent_test, list_test_scenarios, or get_agent_test, so routing between siblings is left to inference.

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.

Resources