Skip to main content
Glama
STREONOR MCP

STREONOR MCP

by lde-medeiros

restore_controls

Destructive

Restores a previewed stream controller controls backup and backs up current controls before replacement. Use it to revert control configurations while preserving the existing setup.

Instructions

Restore a previewed control backup. The current controls are backed up before replacement.

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": {
      "profile": "<profile>",
      "backup_name": "<backup_name>",
      "expected_sha256": "<expected_sha256>",
      "expected_backup_sha256": "<expected_backup_sha256>"
    },
    "name": "restore_controls"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNo
profileYes
manage_appNo
backup_nameYes
force_closeNo
expected_sha256Yes
expected_backup_sha256Yes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.8.2

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the replacement behavior is known; the description adds genuine value by noting the current controls are backed up first, mitigating the destruction risk. It says nothing about the required expected_sha256/expected_backup_sha256 concurrency tokens, force_close behavior, or what happens if the current state changed since preview.

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?

Two tight sentences with the operation front-loaded and the safety note second; nothing is wasted. It could be marginally better structured by naming the prerequisite tool and the state-change check.

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 destructive, 7-parameter mutation with no output schema and no parameter documentation anywhere, the description is too thin. It covers the backup safety net but leaves the integrity-check tokens and force_close semantics unexplained, so an agent cannot confidently construct a call.

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

Parameters1/5

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

All 7 parameters have 0% schema description coverage, and the description explains none of them. The two required SHA-256 tokens, force_close, manage_app, and page are completely opaque, which is a serious gap given they gate a destructive restore.

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: 'Restore a previewed control backup.' The word 'previewed' implicitly ties it to the preview step and distinguishes it from preview_control_restore, though it never names that 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 Guidelines3/5

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

'A previewed control backup' implies the prerequisite that a preview must exist first, which is useful implied guidance. There is no explicit statement of when not to use it, what to do on failure, or how it relates to the other apply_* siblings.

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