Skip to main content
Glama
Sign In

Connections

by icu.connections
OverviewDiscussionsAdmin

Script Vault: restore a deleted script

connections_script_restore
Idempotent

Put a deleted Script Vault script back from Trash - code, parameters and description exactly as they were, under the same tool_name. A delete keeps it for your plan's Trash window. WITHOUT tool_name: list this company's deleted scripts still kept. Answers already_exists when a script of that name was saved since (delete or rename that one first), and the upgrade door when the script is past your plan's Trash window.

Input Schema

NameRequiredDescriptionDefault
personNoLinked person to run this call as (first name). Omit to run as the connection's holder.
projectNoWorkspace to run this call in (id or name).
script_idNoRestore by the script_id the list returned, when one name was deleted more than once.
tool_nameNoThe deleted script to restore. Omit to list deleted scripts.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / person
      Added value: +{
+  "description": "Linked person to run this call as (first name). Omit to run as the connection's holder.",
+  "type": "string"
+}
  2. Changed1 schema field changed
    • addedInput schema / properties / project
      Added value: +{
+  "description": "Workspace to run this call in (id or name).",
+  "type": "string"
+}
  3. Added

TDQS

A4.3/5.0
Behavior5/5

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

With annotations covering safety (idempotent, non-destructive, write), the description adds substantial context: what gets restored (code, parameters, description exactly as before), the Trash-window retention rule, and two named error outcomes (already_exists, upgrade door). This is well beyond what the annotations provide.

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?

Front-loads the restore action, then layers the list mode and error cases in a compact block. Slightly dense with multiple clauses but each sentence carries distinct, useful information; no filler.

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?

No output schema, but the description explains what is restored (code, params, description) and the key edge-case responses, and annotations carry the safety profile. Minor gap: it doesn't describe the success return shape or the deleted-list output, but overall it is complete enough for a 4-param, zero-required tool.

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 coverage is 100%, so tool_name, script_id, person, and project are all already documented. The description restates the tool_name-omit-to-list behavior already present in the schema and adds no new semantics for script_id or person beyond the schema, so the baseline 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb+resource ('Put a deleted Script Vault script back from Trash') and clarifies the dual mode (omit tool_name to list). It is clearly distinguishable from siblings like connections_script_delete, connections_script_get, and connections_script_save without opening any schema.

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

Usage Guidelines4/5

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

Clearly conveys when to restore versus when omitting tool_name switches into listing deleted scripts, and explains preconditions for two failure paths (already_exists, past Trash window). It stops short of naming sibling alternatives for those error cases, so not a full when/when-not mapping.

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

All Connections toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources