Skip to main content
Glama

record_stop

Stop recording a 5250 session and return the captured flow as YAML, optionally saving it as a reusable tool to review before use.

Instructions

Stop recording and return the flow as YAML (saved when the server has a record folder). The flow is available as a tool right away. Review it before relying on it.

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": "record_stop"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoflow name (lower_snake_case); leave out to discard the recording
saveNowrite <name>.yaml to the server's record folder
paramsNoauto: typed values become parameters (recorded value = default); none: keep them literalauto
sessionNosession name; lets you run several side by sidemain
descriptionNowhat the flow does; the agent reads it when choosing tools

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations declare readOnlyHint=false and destructiveHint=false, so the bar is lower, but the description does add real context: the YAML is only persisted when the server has a record folder, and the flow becomes callable as a tool immediately. It omits the discard behavior when name is omitted and any error/permission conditions, leaving meaningful behavioral gaps.

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 sentences, front-loaded with the core action and result, with no redundant restatement of the name. The final caution line is slightly soft but earns its place as a usage note.

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

Completeness4/5

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

With annotations present, five fully documented parameters, and an output schema covering the return value, the description supplies the remaining essentials: the YAML return, conditional saving, and immediate tool availability. Only error and discard conditions are unaddressed, which is a minor gap.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3; the description indirectly clarifies the output artifact (YAML) and its persistence condition, which reinforces the meaning of the save/name parameters. It adds little explicit parameter semantics beyond that, keeping it modestly above baseline.

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 ('Stop recording') and the primary return value ('return the flow as YAML'), which cleanly contrasts with the sibling record_start. It stops short of naming record_start as the prerequisite, so it is clear but not fully differentiated in text.

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?

Usage is only implied: you stop a recording that was started, and the closing line advises reviewing the flow before relying on it. There is no explicit when/when-not guidance or reference to alternatives such as record_start.

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